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

[Torgny Nyblom]

On Wed, 8 Sep 2010 18:56:24 +0200
Thomas Zander <zander at kde.org> wrote:

> On Wednesday 8. September 2010 16.09.48 Ian Monroe wrote:
> >  Glad to hear it though.
> > Certainly means that creating the rules file for monolithic repos
> > isn't less work then split repos, either way we have to track all
> > the project movement.
> 
> Wrong; the tracking of individual apps or tracking of whole projects
> (i.e. subdirs at a time) is a big difference in amount of effort.
> Imagine code moving from koffice/libs/pigment to koffice/plugins
> requires no rules to write (since its all under one subdir and git
> handles those moves without being told to) or having to track those
> movements yourself in explicit rules.
> 
> The difference is that in-module moves are part of history and should
> be kept as moves. Whereas split modules require you to figure thouse
> out and you essentially have to rewrite actual history.

Tracking this example in two repositories also means that if you go back
then you will have a non building copy since the files are there in one
repository but they lived in the other in that point in time.

Or in short tracking an application is rather easy either way, tracking
an application that has seen heavy refactoring into libraries will be a
pita if those libraries are to be in a different repository.

/Regards
Torgny