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

[Christoph Cullmann]

On Wednesday, September 08, 2010 01:48:48 am Chani wrote:
> > > > I agree on the general direction, the split approach just makes it
> > > > much more easy for people working on individual apps to contribute
> > > > by avoiding to clone everything.
> > > > 
> > > > For Kate for example that still would mean to split out the part and
> > > > ktexteditor interfaces from kdelibs, which is already done in the
> > > > gitorious kate repo, which bundles part/app/kwrite and ktexteditor
> > > > interfaces for the part.
> > > 
> > > the way I read it, that wasn't part of the sysadmins' proposal; kdelibs
> > > was to be kept intact.
> > 
> > Christoph doesn't suggest to split kdelibs. All he suggests is to move
> > kdelibs/kate and kdelibs/interfaces/ktexteditor to the own Kate module.
> > We
> 
> I ... don't see how moving something out of kdelibs isn't splitting kdelibs
> :)
It was there, because of historical reasons, but in fact, katepart and 
ktexteditor are used nowhere in kdelibs.
The part is anyway only runtime dep and the interfaces are its public API.

> 
> > are practicing this for more than half a year now anyway, and have
> > tremendous success with that. It's so easy to build Kate with just some
> > commands - we really really would like to keep it that way [1].
> > 
> > And the good news is that nothing in kdelibs depends on Kate or the
> > KTextEditor interfaces. So technically this is no issue.
> 
> but don't kdebase and kdevelop depend on the katepart? that'd mean they'd
> have a dependency on kate as well as kdelibs... :/
Yes, and where is the problem?

> 
> anyways, I'm getting offtopic. it just concerns me a bit, kate being split
> off from the rest of kde like that..
I heard that already as we went to gitorious, but, fact is: it works well, to 
have the three parts in one place: part, interfaces + app.
Its not a lot of code and it is strongly connected and the developer group is 
equal.
We got nice patches for the git repo, and it would make in my eyes no sense to 
force people to clone kdelibs just to make a kate patch.

My only concern is: I would like to just stay in the KDE release cycle, as for 
example for ktexteditor that is required.
And I am not sure how much additional work a own "kate" module would create 
for the release team :/
Otherwise it is a no-brainer that this grouping makes sense.

Greetings
Christoph

-- 
-------------------------------------- Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH      Email: cullmann at AbsInt.com
Science Park 1                         Tel:   +49-681-38360-22
66123 Saarbrücken                      Fax:   +49-681-38360-20
GERMANY                                WWW:   http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234