1 |
On Sat, Sep 6, 2014 at 8:41 AM, Patrick Lauer <patrick@g.o> wrote: |
2 |
> |
3 |
> And by the same reasoning of "bloat" we should remove openssh ( and maybe even |
4 |
> rsync ;) ) because it's not strictly needed - so maybe we want a "minimal" and |
5 |
> a "useful" stage3 ? |
6 |
|
7 |
I could care less what is in the stage3, which only affects the |
8 |
content of a gentoo system for its first 5 minutes of existence. I |
9 |
care more about what is in the system set. Right now they're forced |
10 |
to be the same thing. bit there is no reason that this has to be so. |
11 |
|
12 |
If the stage3 bundles a bunch of stuff that either goes away at the |
13 |
first --depclean or is just part of the initial world and can be |
14 |
trivially removed (and there are no issues with parallel builds), then |
15 |
I don't have a huge problem with it, though I still think that openssh |
16 |
in the stage3 is overkill. |
17 |
|
18 |
Minimal vs useful is certainly a good distinction, but just as with |
19 |
the whole server profile debate the definition of useful varies |
20 |
considerably. I think that what would make the most sense is to |
21 |
implement mix-ins so that everybody and their uncle can maintain their |
22 |
own personal idea of a useful layer, and then strip the stage3 down to |
23 |
what you really need to bootstrap a system, and limit the system set |
24 |
to the stuff we really don't want to stick in every *DEPEND (libc, |
25 |
baselayout, etc). |
26 |
|
27 |
Trying to get everybody to agree on what is "useful" just leads to |
28 |
endless bikeshedding - better to just let everybody or every project |
29 |
have their own way and let everybody decide which way works for them. |
30 |
|
31 |
-- |
32 |
Rich |