[Kde-scm-interest] Package splitting

Oswald Buddenhagen ossi at kde.org
Tue Jan 26 14:11:13 CET 2010

On Tue, Jan 26, 2010 at 01:47:51PM +0100, Thomas Zander wrote:
> On Tuesday 26. January 2010 11.51.38 Oswald Buddenhagen wrote:
> > well, quite frankly, i was recently rather pissed off by that just
> > configuring kdeutils (to build kcalc and nothing more) required me
> > to install a full-blown kdepimlibs (or hacking the cmake files).
> > don't you think that there is something wrong with that?
> Completely orthogonal; the problem you describe has to do with bad
> dependency checking for compile, not about splitting up sources you
> get.
you got it completely wrong. the *core* of the issue is the assumption
that the module is atomic, so there is supposedly no need to decouple
the dependencies. to fix it, one needs to make every sub^n-module
self-contained buildsystem-wise. and guess what? once that is done, you
also have units which naturally fit separate git repositories. one may
still put a meta-structure over that to simplify checking out "all of
kde", to emphasize project hierarchies, etc., but the point is that at
this time it is totally optional.

More information about the Kde-scm-interest mailing list