[Kde-scm-interest] Package splitting

[Thiago Macieira]

Em Quarta-feira 27. Janeiro 2010, às 22.46.52, Thiago Macieira escreveu:
> Q: What are the flaws in this design?
> A: Points not addressed:
>  - most libraries depend on Qt, but if Qt is in KDE Support, then there's
> an  order problem
>  - it's impossible to have addons/plugins to apps
>  - it's impossible to have libraries depend on other libraries
> And other stuff I've missed.

And here's a suggestion to address those points, so a modification to the rules 
in the earlier email.

Instead of having 4 stages per category, we actually have:

	libs
	libs2
	libs3
	...
	release
	release2
	release3
	...
	review
	playground

The build order is like this:
	libsX before libsY for X < Y
	libsX before releaseX
	releaseX before releaseY for X < Y
	libs* and release* before review
	review before playground

That means we could place Qt in "libs", the rest of current kdesupport in 
"libs2"; kdelibs in KDE Base/libs, but the experimental kdelibs-depending stuff 
in KDE Base/libs2.

We could place Konqueror in KDE Base/release, but konq-plugins in KDE 
Base/release2 (same for Plasma and its addons).

-- 
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/e6211e16/attachment.sig