[Kde-scm-interest] Sysadmin advice regarding Monolithic vs Split repositories.

Sune Vuorela nospam at vuorela.dk
Wed Sep 8 10:02:43 CEST 2010


On 2010-09-07, Dominik Haumann <dhaumann at kde.org> wrote:
> Christoph doesn't suggest to split kdelibs. All he suggests is to move 
> kdelibs/kate and kdelibs/interfaces/ktexteditor to the own Kate module. We 
> are practicing this for more than half a year now anyway, and have 
> tremendous success with that. It's so easy to build Kate with just some 
> commands - we really really would like to keep it that way [1].
>
> And the good news is that nothing in kdelibs depends on Kate or the 
> KTextEditor interfaces. So technically this is no issue.
>
> Besides, Kate would continue to be released with KDE just like now, so it 
> should be perfectly safe even if we have our own module :)

I think moving stuff in or out of kdelibs is not something to be decided
in this maillist, but a topic for k-c-d.

And note that you cannot move things out of kdelibs (except to maybe
move them to kdesupport), but *never* the other way. Else we don't keep
binary compatibility of kdelibs as a whole.

/Sune



More information about the Kde-scm-interest mailing list