On Saturday 16 June 2007, Alexander Skwar <[EMAIL PROTECTED]> 
wrote about '[gentoo-user]  Re: Re: Finer grained kde*-meta packages':
> ยท Boyd Stephen Smith Jr. <[EMAIL PROTECTED]>:
> > Right, because kde*-meta is supposed to replace, and act as much as
> > possible like the monolithic kde* package.  If you don't want all of
> > kdenetwork you don't install kdenetwork-meta, you install individual
> > applications from kdenetwork.
>
> Well, but as kdenetwork-meta is a dependency of kde-meta, this
> "solution" means, that about 300 packages should be manually
> listed, just because one package is not wanted.

No, because as I covered in my other reply, you can still use kdebase-meta, 
kdepim-meta, etc. to pull is all the packages from those parts of kde and 
only list individual applications from the parts you don't want everything 
from (in your case you should be able to use every kde<foo>-meta 'cept for 
kdenetwork-meta).  For your particular use case it's still < 30 packages, 
not 300.

Sure, maybe that's still too many.  Perhaps a "recommends"/"suggests" 
dependency type (all recommends would be post-dependencies) to allow a 
package to install even if all of the packages that satisfy one of it's 
recommend atoms are masked would be better, but you'll have to take that 
up with the developers responsible for specifying the EAPI levels.  
Careful how you phrase any suggestion though or you'll just get shouted 
down by "Gentoo isn't Debian" replies.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
[EMAIL PROTECTED]                      ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.org/                      \_/     

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to