On Fri, May 11, 2012 at 12:55 PM, Sebastian Trüg <[email protected]> wrote:
> Sounds great. However, it requires one more step: > > Create the new repositories we decided on a while ago for the kcm, the > kio slaves and such. This basically means to do "git filter-branch"[1] > as I did for nepomuk-core. > Have fun :) Btw, what do you want to call it? nepomuk-kde? I think we should even include the stuff from kdelibs/nepomuk/utils/. > > [1] > > http://gbayer.com/development/moving-files-from-one-git-repository-to-another-preserving-history/ > > On 05/10/2012 09:32 PM, Vishesh Handa wrote: > > Does anyone have any objections to the current plan? > > > > * Remove kde-runtime/nepomuk > > * All nepomuk development happens in nepomuk-core > > * nepomuk-core will install everything with a Nepomuk2 namespace > > * Applications will have to explicitly depend on nepomuk-core if they > > want to use the new APIs > > > > The old APIs will continue to work exactly the way they work right now. > > > > -- > > Vishesh Handa > > > > > > > > _______________________________________________ > > Nepomuk mailing list > > [email protected] > > https://mail.kde.org/mailman/listinfo/nepomuk > _______________________________________________ > Nepomuk mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/nepomuk > -- Vishesh Handa
