1 |
On Fri, Sep 5, 2014 at 4:30 PM, Anthony G. Basile <blueness@g.o> wrote: |
2 |
> On 09/05/14 16:08, Michał Górny wrote: |
3 |
>> |
4 |
>> Dnia 2014-09-05, o godz. 12:34:11 |
5 |
>> William Hubbs <williamh@g.o> napisał(a): |
6 |
>> |
7 |
>>> there is a bug open requesting that we add sys-apps/iproute2 to the |
8 |
>>> system set [1]. Originally the request was to drop net-tools, but it has |
9 |
>>> become just adding iproute2. |
10 |
>>> |
11 |
>>> If no one objects, I would like to do this sometime in the next 72 |
12 |
>>> hours by adding sys-apps/iproute2 to profiles/default/linux/packages. |
13 |
>>> |
14 |
>>> Thoughts? |
15 |
>> |
16 |
>> I object. We should be keeping towards making @system as small |
17 |
>> as possible, not adding random packages there just because someone |
18 |
>> happens to use them often. |
19 |
>> |
20 |
> |
21 |
> I don't like to say no when people want something, but I think here I'm with |
22 |
> Michal. My idea of @system is that it must be the bare minimum to have a |
23 |
> "working" system. And for a working system you need just enough toolchain, |
24 |
> networking and python to be able to bootstrap into whatever you want to |
25 |
> build from that point. We already have net-tools, so iproute2 is not |
26 |
> needed. |
27 |
> |
28 |
> Why can't you just emerge iproute2 from the stages we already have? |
29 |
> |
30 |
|
31 |
You can, and I do... every time I unpack a stage3 tarball. |
32 |
|
33 |
Keeping @system minimal seems like a reasonable ideal though. |