[Kde-scm-interest] Package splitting

Oswald Buddenhagen ossi at kde.org
Wed Jan 27 13:51:10 CET 2010

On Wed, Jan 27, 2010 at 12:38:21PM +0100, Thomas Zander wrote:
> I've had too many accusations of breaking the build in koffice just because the 
> user updated only his app and forgot to type 'svn update' in the libraries.
well, quite frankly: tough luck. for him. the advantage of non-atomicity
is that the user has the *option* to do only a partial update, at his
own risk. not everyone has a compile cluster at his fingertips to always
pull everything without thinking much about it.

if you extrapolate your argument (which would be just logical, as
kdebase devs are often enough accused of breaking the build by adding
dependencies on recent kdelibs functionality), it would mean that the
entire KDE/ needs to be in one repository. i think you agree that this
too absurd to even consider.

the solution to the problem seems to be updating the supermodule if
atomicity is needed, and have git notice that it needs to pull the
supermodule and respective submodules when the update of one submodule
tries to break the atomicity. dunno if git can do that right now, but it
sure sounds like something you'd want to fix if not. ;)

> The same happens on backports, though they tend to have a worse effect as 
> those break it for everyone else too.
what scenario do you have in mind here?

More information about the Kde-scm-interest mailing list