organizing kdebase

[Aaron J. Seigo]

On February 22, 2007, Richard Moore wrote:
> Anything kdebase will be in one of these groups:
>
> a) Present on all platforms for KDE applications to operate
> b) Present to allow non-KDE apps for a particular platform to integrate
> c) Part of the KDE desktop environement itself

d) apps expected on a minimal desktop, but which are part of the desktop env 
itself

> a == apps

a == runtime, actually

> b == ??
> c == workspace
>
> Is this a better way of looking at things?

i think it is essentially how i'm looking at it, yes. from a packager's POV 
the stuff in runtime/ are the dependencies for KDE apps. the stuff in utils/ 
(or tools/, or whatever) is useful for scripts, apps and command line users 
which aren't KApplications. they are so useful they are in kdebase, but they 
aren't dependencies for KApplications.

this is useful information for both developers of KDE apps (e.g. if it isn't 
in runtime, what are you doing using it? and if it is in runtime, respect it 
even more when modifying it!) as well as system integrators ("this is what 
KDE apps rely on", "this is a set of essential integration and command line 
tools KDE provides", "this is a basic set of apps", "this is the workspace 
or 'desktop shell' ")

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

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070222/e41fb8fc/attachment.sig>