[Kde-scm-interest] Package splitting

[Thiago Macieira]

Em Quarta-feira 27 Janeiro 2010, às 14:33:48, Oswald Buddenhagen escreveu:
> On Wed, Jan 27, 2010 at 02:12:26PM +0100, Michael Jansen wrote:
> > On Tuesday 26 January 2010 23:50:51 Matt Williams wrote:
> > > What are we going to do about being able to move applications from one
> > > KDE logical project to another? e.g., how will we be able to move a
> > > new application from playground to kdereview to kdegames while
> > > preserving history?
> > 
> > Noone willing or able to anwer this question? I'm very curious too.
> 
> that's because i have answered it before. :)
> when everything is properly split, "moving" will be nothing more than a
> matter of updating two metamodules.
> if it is not split up, everyone gets f****d. any more questions? ;)

Yep.

The idea was:

We have a flat structure in the server:

akonadi.git
soprano.git
kdelibs.git (I don't agree about splitting this one, so bear with me)
kwin.git
kglobalaccel.git
plasma.git
konsole.git
konqueror.git
dolphin.git
kopete.git
kmix.git
amarok.git
konversation.git
someplaygroundapp.git
somereviewapp.git
etc.

Then we have this "manifest" file somewhere that indicates:

- akonadi and soprano are part of "KDE Support" metamodule
- kdelibs, kglobalaccel are part of "KDE Base" (i.e., libs + runtime)
- plasma, kwin are part of "KDE Workspace"
- konqueror, dolphin, konsole are part of "KDE Apps" 
  (or not)
- amarok, kmix are part of "extragear/multimedia"
  (we'd no longer have kdemultimedia)
- kopete and konversation is part of "extragear/network"
  (we'd no longer have kdenetwork)
- someplaygroundapp.git is part of "playground/whatever"
- somereviewapp.git is part of "review/whatever"

When those two pre-release apps move up the food chain, we just need to update 
the manifest indicating where they should be.

Also note that the manifest could indicate the filesystem hierarchy. It could 
be used by an eventual kdegit-build script to clone, check out and update the 
code, to track dependencies, etc.

So to bootstrap your KDE build, you'd clone the repository that contains the 
manifest and the build tool. When you run the tool, it clones the remaining 
repositories. Next time, it'll simply update them.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20100127/2cfd75a6/attachment.sig