-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Armak wrote: | KDE doesn't have any special requirements. It doesn't use any kind of X11 | build tool (what is there other than imake?). It does use some X apps like | xmessage, xset etc. After you commit your metaebuilds we'll update the deps | as needed. The only metaebuild we'll need to depend on is -libs.
I'd prefer that people don't come to depend on metabuilds at all. See http://dev.gentoo.org/~spyderous/xorg-x11/porting_to_modular_x_howto.txt. | However, consider this usecase: user (who's used to the old docs) installs new | stage3, types 'emerge kde', runs kdm... oops, no X server... | | To keep the current behaviour, the kde metaebuild (and gnome and the other | WMs) would have to depend on xorg-x11, which strictly speaking is | unnecessary. Opinions? How can we educate the users to manually 'emerge | xorg-x11'? Personally I'm in favor of updating the docs, making a big | announcement on all channels, and preparing a nice bug to close duplicates | against. Couple of ideas here. 1) We do as you suggest, and make people emerge xorg-x11 2) KDE could add a USE=X and dep X? ( xorg-server ) | We'll also need to educate them about xorg-x11 not installing fonts any | longer. The way I understood your metabuilds.txt, 'emerge xorg-x11 kde' would | result in an unusable system without any fonts at all... We will still install some fonts, but not all, and I'll note that in the metabuilds text. Thanks for the comments, Donnie -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDV+PhXVaO67S1rtsRAryFAJ4rQJ1FNcnDDiw0gYDAhUwGPFx9vACeOGor uc7ieRH+D73hVLXt8hxAJF4= =MNDF -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
