[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: what packages do we want distros to ship ?
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2008-12-23 6:13:53
Message-ID: 200812222313.56883.aseigo () kde ! org
[Download RAW message or body]


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 
easy for 3rd party apps to depend on them alone:
	* solid
	* threadweaver
	* phonon (ok, not part of kdelibs anymore, but you get the idea =)

* the core kdelibs: core, ui, kio/kfile, kded, knewstuff, etc... libs that are 
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 
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 
an atomic unit

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

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

just mho =)

-- 
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


["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]