1 |
On Wed, Oct 26, 2016 at 10:54 PM, Walter Dnes <waltdnes@××××××××.org> wrote: |
2 |
> On Thu, Oct 27, 2016 at 01:10:10AM +0000, Peter Stuge wrote |
3 |
>> waltdnes@××××××××.org wrote: |
4 |
>> > For a build-from-source distro like Gentoo, gcc and associated |
5 |
>> > tools are a vital part of the distro. |
6 |
>> |
7 |
>> A stage4 created (and updated) on a catalyst build farm doesn't need |
8 |
>> to have gcc, but may still need libstdc++. |
9 |
> |
10 |
> That just moves the requirement for gcc+tools to the catalyst build |
11 |
> farm. OK, let's get specific... a *STANDALONE* Gentoo machine requires |
12 |
> gcc+tools. |
13 |
|
14 |
This is why I think "@system" oversimplifies all of this. IMO we |
15 |
should just specify all dependencies for everything (and those could |
16 |
include some virtuals for convenience, like the C toolchain), and then |
17 |
have different sets or virtuals for convenience. By all means give a |
18 |
user with a default install that sticks virtual/common-packages or |
19 |
something in their @world. Nobody is arguing that the typical Gentoo |
20 |
user doesn't want gcc, or that we should force people to explicitly |
21 |
install it. |
22 |
|
23 |
Fixing the dependencies means that system packages can take advantage |
24 |
of parallel builds, which means faster updates for everybody. We can |
25 |
still have sets for bootstraping (and I suspect that having more |
26 |
virtuals or sets would allow stage1/2 definition to be simplified). |
27 |
|
28 |
It is a bit like license groups. We give everybody a default set of |
29 |
license groups that generally makes sense. But, if you want you can |
30 |
easily edit your make.conf to exclude anything that is copyleft from |
31 |
your system. |
32 |
|
33 |
The main downside to this is it is a bit more of a hassle for |
34 |
developers to maintain the dependency lists, since invariably you end |
35 |
up with a lot of mundane stuff in there. And of course it is a lot of |
36 |
change to implement, though it could be done gradually. And of course |
37 |
the upside for the typcal user is somewhat limited, since most people |
38 |
aren't dying to uninstall openssh or gcc. |
39 |
|
40 |
-- |
41 |
Rich |