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

[Ingo Klöcker]

On Wednesday 08 September 2010, Ian Monroe wrote:
> On Wed, Sep 8, 2010 at 7:34 AM, Tom Albers <toma at kde.org> wrote:
> > Again, we advise you to go for a split approach, if the list does
> > not want that, it is fine. Just solve the problems we address in
> > the document and accept the technical consequences it will have.
> > To turn this around: don't discourage us to write such documents
> > in the future, I think it contributes to the discussion and is
> > therefore valueable.
> 
> Well as already addressed, much of the issues listed in the document
> are invalid since no one was ever proposing there literally be a
> kdereview or a playground repo.
> 
> Lets make this a bit more specific: what is the proposed hierarchy
> for kdebase?
> 
> Furthermore, since the KOffice folks always seemed to like to stay in
> one repo to enable them to make commits touching multiple apps, would
> having a single KOffice repo be possible? I understand this would
> make Redmine a bit confusing, but treating KOffice as one Redmine
> project isn't the end of the world.
> 
> Personally I think the case for things like KDE Multimedia, KDE
> Bindings, KDE Edu to each be a single repo is pretty weak. If partial
> checkouts of a SVN repo are common, then the case for split repos are
> quite strong. But things maybe get more complicated with kdebase and
> koffice, for technical and cultural reasons.

You can add kdepimlibs, kdepim and kdepim-runtime to the list of repos 
where splitting them into smaller repos doesn't really make much sense 
since they are so strongly intertwined. In fact, I don't see how the 
approach of split repositories makes sense for modules which have 
_internal_ libraries (kdepim is full of internal libraries) that are 
shared by several apps.

Do the sysadmins have an advice how to handle internal libraries?


Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20100908/f3f9c980/attachment-0001.sig