--nextPart17111202.ro2PWuGAdn
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 22 December 2008, Alexander Neundorf wrote:
> My guess is that it's somewhere in between, e.g. whole kdelibs,

kdelibs could probably be broken out a bit, in particular:

* the libs that have no deps on KDE could be packaged individually, making =
it=20
easy for 3rd party apps to depend on them alone:
	* solid
	* threadweaver
	* phonon (ok, not part of kdelibs anymore, but you get the idea =3D)

* the core kdelibs: core, ui, kio/kfile, kded, knewstuff, etc... libs that =
are=20
so commonly used and which make kde apps kde apps.

* non-core significant libs could be packaged on their own:
	* khtml+kjs
	* plasma
	* kross
	* kformula

kdebase should probably be split into:

* runtime; there's no point in having only part of this. the whole idea is=
=20
that these are the things apps must be able to rely on being there.

* workspace; maybe a libs+apps split, but this again makes most sense to me=
 as=20
an atomic unit

* apps: libs in one package (libkonq), applications individually packagable=
:=20
konq, dolphin, konsole, etc

for the other modules, i imagine it makes sense to do full package or=20
individual apps.

just mho =3D)

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software


--nextPart17111202.ro2PWuGAdn
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAklQgaQACgkQ1rcusafx20P7fACgiTjbbYgTLZ50xZDccVkuSycb
vE0AoIwtcb1Nnqzw/LIxSFL97bJLbJi8
=hgRA
-----END PGP SIGNATURE-----

--nextPart17111202.ro2PWuGAdn--