The Nepomuk Situation

[Albert Astals Cid]

El Dimecres, 2 de maig de 2012, a les 12:14:00, Ivan Cukic va escriure:
> > The first solution -
> > * Remove nepomuk from kdelibs and kde-runtime
> 
> +1 This is what has been done with kactivities. Instead of having it in
> kdelibs and runtime, it is now all in one repository.
> 
> The only difference here is that nepomuk is not in libs/experimental like
> libkactivities was.

This is a huge difference, we *promise* to keep SC and BC of our libs, doing 
the first solution would totally go against our promises.

Cheers,
  Albert

> 
> I think that this would help KF5 efforts since applications would start
> porting early to the new libraries. Again, the only downside being the fact
> that libnepomuk will not be able to stay binary (or api) back-compatible due
> to uses of KUrl and similars (it it hasn't already been removed in the
> nepomuk-core)
> 
> Cheerio,
> Ivan
> 
> > * 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)
> > 
> > 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-
> > se rvice/