Separating everything ?

[Alexander Neundorf]

On Friday 08 February 2013, Martin Sandsmark wrote:
> On Fri, Feb 08, 2013 at 01:10:20PM +0100, Mirko Boehm wrote:
> > I am mostly arguing that to achieve 1) and 2), we do not have to have 3),
> > a multi-repository structure. It can all be achieved by email.
> 
> Still leaves the fact that kdelibs currently is 188MB (and it is not going
> to shrink) which is very painful, especially on a subpar internet
> connection (as git can't resume).

IMO this is very much not a black-and-white situation.
It is not "leave everything in one huge blob as it is now" vs. "put every tiny 
library in its separate repository", there are steps in between.

I for one would prefer if we stay with a moderate number of repositories.
khtml e.g. is big, this should be separate (will it actually still exist ?). I 
would guess the "solutions" each deserve a separate repository.

Just a bunch of libraries can happily live together in one repository, and 
optionally also be built in one step.
Have a look e.g. at the current state of kdelibs/tier1/.
Those can (since a few days) be built and installed completely separately.
Next to them I added a directory superbuild/, mainly for my own convenience, 
to build them all in one go.
If you simply run cmake there, nothing is built, you have to explicitely 
enable the libs you want to build, and there are not dependencies between 
them, so this is simple and straightforward.
Those together are still small, fast to download, and easy to package 
separately.

I don't see an advantage in splitting such things into separate repositories.

Alex