[Nepomuk] The Nepomuk Situation

[Christian Mollekopf]

> On Thursday 03 May 2012 00.32:37 Vishesh Handa wrote:
> 
> Hey everyone!
> 
Hey Vishesh,

Glad your tackling this, it's indeed a rather painful situation.

> 
> So, we need a solution.
> 
> The first solution -
> * Remove nepomuk from kdelibs and kde-runtime
> * Make nepomuk-core a compile time dependency for kdelibs
> * Including the missing gui code into nepomuk-core
> 
> The second solution is -
> * nepomuk-core installs the headers in nepomuk2
> * the library already has a different name, so there are no clashes over 
there
> * kde-runtime/nepomuk is removed
> * nepomuk-core is added as a dependency of kde-runtime
> 
> The problem with the second solution is that all applications using Nepomuk 
will also need to depend on nepomuk-core. So far the list includes - Dolphin, 
KDE-pim and Telepathy (kinda)
> 

I would suggest to create two repostories. One "nepomuk-core" containing the 
dependencies of kdelibs (respectively nepomuks core libraries), and another 
one "nepomuk2" containing the dms and possibly other stuff which depends on 
kdelibs (and in the future the required parts of kf5). That would give you 
clean dependencies without copies of code, which I think would be rather ugly 
(assuming that the "missing gui code" would be a copy of kdelibs code).

I don't see any problem with applications having to depend on nepomuk 
libraries when they're using it. In contrary I would welcome repositories 
which keep dependencies low, as that opens new possibilities, such as using 
the same libraries in a server environment where you don't want to pull in 
everything including X11.

Cheers,
Christian

> What do you guys think?
> 
> [1] https://projects.kde.org/projects/kde/kdelibs/nepomuk-core
> [2] http://trueg.wordpress.com/2011/06/08/nepomuk-2-0-and-the-data-
management-service/
> 
> -- 
> Vishesh Handa
> 
> 
> 
> 
>