Require Soprano for kdelibs

[Aaron J. Seigo]

On Thursday 06 August 2009, Volker Krause wrote:
> However, experience with that in KDE PIM (eg. cyrus-sasl for various mail
> server authentication methods, to name just one example) shows that this
> can cause considerable support load since not everyone pays attention to
> the CMake output regarding the effects of missing dependencies. If I can't
> even rely on distros doing that correctly (most of them do fortunately), my
> only option to ensure that the majority of our users get a fully working
> application is to enforce the dependencies unfortunately :-/

and in the case of things like plasma-desktop/plasma-netbook and where the 
feature sets are going there, there will soon be code in libplasma that allows 
those UI shells to coordinate context with the rest of the system via nepomuk.

i really think that the semantic/social/contextual system is going to become 
more of a core feature than a "nice to have" add-on as we continue on.

and yes, if there's some comparable system-specific framework we could rely on 
and we can pull a Solid/Phonon style API over it that'd be great, but afaik 
the Soprano / Nepomuk duo are fairly unique in that area as far as production 
systems go.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090806/706d8b33/attachment.sig>