| 1 |
On 10/15/2015 02:51 PM, Anthony G. Basile wrote: |
| 2 |
> On 10/15/15 5:20 PM, Zac Medico wrote: |
| 3 |
>> On 10/15/2015 02:13 PM, Mike Frysinger wrote: |
| 4 |
>> |
| 5 |
>> so if iputils is in @profile, and i do: |
| 6 |
>> emerge -C iputils |
| 7 |
>> i don't get the ugly warning about it being in @system, but if i do: |
| 8 |
>> emerge @world |
| 9 |
>> iputils comes back. i think that's OK actually since people can do: |
| 10 |
>> emerge @selected |
| 11 |
>> which has the classic @world meaning. |
| 12 |
>> -mike |
| 13 |
>> |
| 14 |
>> People need to be able to use @world without it pulling in unwanted |
| 15 |
>> packages, since it's the only way to properly do a full update of all |
| 16 |
>> relevant packages (relevant packages being those that would not be |
| 17 |
>> removed by depclean). |
| 18 |
> But that's true of @system packages now. If a user does `emerge -C |
| 19 |
> iputils` they get a warning about it being in the system set and when |
| 20 |
> they do `emerge @world` it comes back. |
| 21 |
|
| 22 |
I think it's obvious that such packages don't belong in @system, unless |
| 23 |
we're talking about a profile where iputils is absolutely required for |
| 24 |
some reason. |
| 25 |
|
| 26 |
> The only change in moving it to @profile is the warning. |
| 27 |
|
| 28 |
What's the point of getting rid of the warning if the package is going |
| 29 |
to get pulled back in on the next @world update? Either way, the end |
| 30 |
result it that the user has to go through some hoops |
| 31 |
(/etc/portage/profile overrides) if they don't want that package |
| 32 |
installed again. |
| 33 |
|
| 34 |
> Also, I think the other change is during the |
| 35 |
> building of the /tmp/stage1root during stage1, @system won't include |
| 36 |
> iputils and this saves on the number of packages built. |
| 37 |
|
| 38 |
The last time I checked, @system was not used for stage1. Catalyst used |
| 39 |
package.build instead. Has that changed? |
| 40 |
-- |
| 41 |
Thanks, |
| 42 |
Zac |
Archives