From kde-core-devel  Mon May 15 11:25:57 2006
From: Frans Englich <englich () kde ! org>
Date: Mon, 15 May 2006 11:25:57 +0000
To: kde-core-devel
Subject: Re: Concluding the discussion about splitting kdebase
Message-Id: <200605151125.57875.englich () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=114769171511533


Ups, forgot, I have one last thing to ask about.

On Thursday 11 May 2006 22:27, Cornelius Schumacher wrote:
[...]

> * kdebase/coreapps:
>
> apps needed at runtime by all KDE apps, must also run under TWM and Windows
>
> - drkonqi
> - kioslaves
> - kdesu

kcmshell, residing in kdelibs, uses kdesu for loading KCModules in root mode. 
So this would create a dependency for kdelibs on coreapps, at runtime.

kdebase/coreapps is required for running any KDE application, right? So if one 
wants to run a KDE application in any desktop environment one must install 
kdelibs and kdebase-coreapps, that's my conclusion.

If the user can't get around not installing coreapps, why split it? Is the 
only motivation lowered build time for those who develop against trunk and 
who needs the latest changes in trunk?

The package layout affects the whole world(so to speak), while the change in 
build time only affects a handful of us KDE developers. Also, if ones project 
is dependent on central parts of KDE, I'd the chances are high one have to 
re-build coreapps anyway, in order to have the app run properly.

Enlightenment appreciated.


Cheers,

		Frans