On Saturday 18 September 2004 2:16 am, Dan Armak wrote:
> A kde configure script takes as much as a minute or more to run. Today when
> you emerge all of kde you run ~17 configure scripts, i.e. as much as 20
> minutes goes there (of course everything depends on the speed of the
> machine). If all kde-base packages are split into separate subpackage
> ebuilds, you'll get hundreds of subpackags (200+). 

Perhaps instead of using completely independent packages for the software 
applications, a set of "pseudo-packages" could be created to alleviate the 
extra configuration requirements? 

I've previously used the DO_NOT_COMPILE option for the KDE ebuilds and 
successfully screened out many of the unwanted packages. If the dependencies 
for any given software application were known (herein lies the large amount 
of maintenance), it should then be possible to manipulate that environment 
variable to only compile what is necessary for the user. Granted it would 
take a fair amount of script-work, however it's an option to consider.


> And most people do want the whole of kde.

Unfortunately, I don't fall into the category of "most people" when it comes 
to KDE's software; the above comment is a prime example of why I migrated to 
Gentoo and Linux as opposed to windows.


-- 
Anthony Gorecki
Ectro-Linux Foundation