1 |
On Saturday 16 June 2007, Alexander Skwar <listen@×××××××××××××××.name> |
2 |
wrote about '[gentoo-user] Re: Re: Finer grained kde*-meta packages': |
3 |
> · Boyd Stephen Smith Jr. <bss03@××××××××××.net>: |
4 |
> > Right, because kde*-meta is supposed to replace, and act as much as |
5 |
> > possible like the monolithic kde* package. If you don't want all of |
6 |
> > kdenetwork you don't install kdenetwork-meta, you install individual |
7 |
> > applications from kdenetwork. |
8 |
> |
9 |
> Well, but as kdenetwork-meta is a dependency of kde-meta, this |
10 |
> "solution" means, that about 300 packages should be manually |
11 |
> listed, just because one package is not wanted. |
12 |
|
13 |
No, because as I covered in my other reply, you can still use kdebase-meta, |
14 |
kdepim-meta, etc. to pull is all the packages from those parts of kde and |
15 |
only list individual applications from the parts you don't want everything |
16 |
from (in your case you should be able to use every kde<foo>-meta 'cept for |
17 |
kdenetwork-meta). For your particular use case it's still < 30 packages, |
18 |
not 300. |
19 |
|
20 |
Sure, maybe that's still too many. Perhaps a "recommends"/"suggests" |
21 |
dependency type (all recommends would be post-dependencies) to allow a |
22 |
package to install even if all of the packages that satisfy one of it's |
23 |
recommend atoms are masked would be better, but you'll have to take that |
24 |
up with the developers responsible for specifying the EAPI levels. |
25 |
Careful how you phrase any suggestion though or you'll just get shouted |
26 |
down by "Gentoo isn't Debian" replies. |
27 |
|
28 |
-- |
29 |
Boyd Stephen Smith Jr. ,= ,-_-. =. |
30 |
bss03@××××××××××.net ((_/)o o(\_)) |
31 |
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' |
32 |
http://iguanasuicide.org/ \_/ |