On Friday 29 January 2010 14:36:32 Matt Williams wrote: > > In this way, we won't get a "big bang" split up + migration, which is > > maybe too ambitious, and we would still get the ability to move > > application from review+playground. And the atomicity problems goes away. > > As for dependency hell, I believe one "lib" for each module + kdelibs > > would be a reasonable amount to check for. > > The only problem I see here is how to move a game from kdereview to > kdegames while keeping its history. I've been lead to believe that you > can't incorporate a repo into another one while keeping all the > history. This is also a problem when we want to move libs or apps > out of a module (into playground/unmaintained or another main > module). >
I should have been clearer: My suggestion was to not move any new applications into the modules ever, slowly turning them into libraries-only modules. I think that is the only long-term solution that isn't hackish. -- Kind regards, Esben _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest