[PATCH] Making Soprano optional (again) in kdelibs
Maciej Mrozowski
reavertm at gmail.com
Mon Dec 28 11:24:32 CET 2009
On Sunday 27 of December 2009 19:06:18 Allen Winter wrote:
> From a kdepim point-of-view, Nepomuk must be a hard dependency as
> Kontact will have big problems without it.
>
> So either Nepomuk is a hard dependency for kdelibs or for kdepim.
>
> Might as well keep it a hard dependency for kdelibs.
First things first - Ok to commit the following change making nepomuk
mandatory (sic!) in kdepim (see attachment)?
Also what's desired kdelibs and kdepimlibs version for upcoming 4.4 version of
kdepim (and kdepim-runtime which is as we know distributed separately as
well)?
Currently it's a bit inconsistent (any kdelibs + 4.3.66 kdepimlibs or 4.2.87
in case of kdepim-runtime) - should I set it all to 4.4? (let's say 4.3.85). I
doubt you test it with multiple versions of mentioned packages so maybe
depending on versions you actually use for development (so is 4.4) is more
reasonable.
Also I would like to reorganize flow control in kdepim CMake files so that it
does not force all dependencies on *all* kdepim apps, but only on those who
actually need those dependencies (like it's the case in other better
buildsystem-wise organized modules like kdebase/*, kdeutils etc). For instance
requiring strigi or nepomuk when building knode is incorrect.
--
regards
MM
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdepim-nepomuk.diff
Type: text/x-patch
Size: 6109 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20091228/74256260/attachment.diff
More information about the Kde-buildsystem
mailing list