On Tuesday 18 January 2005 5:45 am, Stuart Longland wrote: > Personally, I'd much rather keep the monolithic packages as the KDE > developers intended.
Reminder: KDE's semi-official view is that the CVS modules (kdebase, kdenetwork, etc) *should* be split into many individual packages. > I think the better way to handle this would be to > set an environment variable... e.g. > > # KDE_PKG='+konqueror +kicker +kdm -kicker' emerge kdebase > > That gives us the best of both worlds -- it allows us to keep the > monolithic packages for one, secondly, users can still pick what they > want from a given package, and thirdly, it doesn't waste any time > running configure scripts repeatedly. Therefore, this should keep > everyone happy. :-) What do others think? Does this have any benefits over the prior (pre-split ebuilds) situation or is it simply changing the env variable for DO_NOT_COMPILE to KDE_PKG? What happens to parts that aren't referenced by either a + or -? -- Luke-Jr Developer, Utopios http://utopios.org/ -- [email protected] mailing list
