1 |
On Tue, Jun 14, 2011 at 8:54 AM, Brian Harring <ferringb@×××××.com> wrote: |
2 |
> The implicit system set dependency thing really, really needs to die; |
3 |
> at the time of the rule, portage couldn't handle resolving graphs of |
4 |
> that sort. PM resolvers for gentoo are generally a fair bit saner |
5 |
> now thus doing what you're suggesting isn't really beneficial (frankly |
6 |
> it causes some issues for stages, as zac noted). |
7 |
|
8 |
++ |
9 |
|
10 |
It seems to me that the best policy would be for every package to just |
11 |
list all its dependencies, and then users are free to run the default |
12 |
experience that includes everything in @system, or a more trimmed-down |
13 |
experience. Plus, from time to time there is some debate about |
14 |
removing some package from @system and the only way to figure out what |
15 |
it breaks is a long discussion on -dev and lots of tinderbox testing, |
16 |
and then lots of ebuilds being modified to add the dependency back in. |
17 |
With explicit dependencies it is trivial to determine. |
18 |
|
19 |
And no, I don't think that Gentoo should fully support reduced-@system |
20 |
builds, but there is no harm in making them more of a viable option. |
21 |
|
22 |
Rich |