structure of kde cvs modules, was Re: libkipi in kdesupport

[Rob Kaper]

On Sat, Mar 13, 2004 at 11:16:04PM +0100, Alexander Neundorf wrote:
> -kdecorelibs would be kdecore, kdeui, kio, kparts and some others, i.e. 
> essential libraries
> -kdeapplibs would be e.g. ksmartcard, kate, khtml, kioslave, libkonq and 
> others, also libkcddb from kdemultimedia and maybe this new libkipi, 
> basically all libraries which are part of kde.
> 
> What would this bring ?

Anything but an integrated desktop environment.

The suggestions in this thread are completely the opposite of what KDE used
to stand for.

Every single time we make a component or application optional, we remove a
layer of functionality from KDE. What this proposal amounts to is to turn
KDE into a widget set that happens to be used by a HTML library and that
happens to have applicationThis and applicationThat.

We'd be back in 1996.

KDE is not just "kdecorelibs" and "kdeapplibs". The KIO slaves, KHTML,
Kicker, Kicker, the application modules: they're all equally part of KDE.

Rob
-- 
Rob Kaper     | 3/19 The Offspring AMSTERDAM, 3/24 Good Riddance AMSTERDAM
cap at capsi.com | 4/29 The Rasmus LONDON, 5/11 Ghost of the Robot AMSTERDAM
www.capsi.com | 5/14 Disney PARIS, 7/19 COPENHAGEN, 7/20 MALMÖ
              | 7/21 STOCKHOLM, 7/23 KÖPING, 8/1 OSLO
-------------- 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/20040317/44ac2a61/attachment.sig>