| 1 |
Rich Freeman posted on Fri, 05 Sep 2014 20:10:02 -0400 as excerpted: |
| 2 |
|
| 3 |
> The purpose of the system set is to deal with circular deps and the need |
| 4 |
> to bootstrap. We shouldn't have stuff in there if it is possible to run |
| 5 |
> without it. |
| 6 |
> |
| 7 |
> There are loads of things I can't live without which aren't in the |
| 8 |
> system set. I have a default world file that I always start with |
| 9 |
> anytime I do an install. |
| 10 |
|
| 11 |
Does portage still force serial builds of anything in the system-set and |
| 12 |
all deps thereof?[1] If so, given a situation where even most phones are |
| 13 |
multi-core these days, does /anything/ other than circular deps and |
| 14 |
bootstrapping really justify forcing /all/ the several @system packages |
| 15 |
and deps I had before I started pruning, into serial build? |
| 16 |
|
| 17 |
And isn't it time to think about something similar to the "-*" for USE |
| 18 |
flags, but aimed at @system instead, so those like me that wish to be |
| 19 |
free of the problem can simply set -* in /etc/portage/profile/packages |
| 20 |
and be done with it, instead of having to negate them one by one, and |
| 21 |
constantly patrol[2] lest a proposal such as this add something else to |
| 22 |
be negated? |
| 23 |
|
| 24 |
I've been running @system-less for quite some time now, two years or |
| 25 |
better I think, and it hasn't killed my system yet. While @system might |
| 26 |
be useful for bringing up a system as well as for the extra warnings on |
| 27 |
@system-set member removal it gives people who need a bit of hand- |
| 28 |
holding, I think it's fair to say that I've demonstrated by now that it's |
| 29 |
entirely unnecessary on a system with a reasonably careful sysadmin |
| 30 |
(careful enough that if something bad /does/ happen, there's several |
| 31 |
levels of tested-bootable backup available that can be used to rescue the |
| 32 |
normal working-boot copy). |
| 33 |
|
| 34 |
And/or, perhaps kill that forced @system serial emerge thing and let |
| 35 |
existing deps take care of things, if it hasn't been done already. At |
| 36 |
least on amd64/nomultilib, it's obviously not necessary or I'd have run |
| 37 |
into issues by now. |
| 38 |
|
| 39 |
|
| 40 |
[1] I wouldn't know, as that's one reason I decided to negate the entire |
| 41 |
system-set and now have an empty @system. |
| 42 |
|
| 43 |
[2] For me, it's when I see emerge --pretend --depclean's empty-system- |
| 44 |
set warning disappear. |
| 45 |
|
| 46 |
-- |
| 47 |
Duncan - List replies preferred. No HTML msgs. |
| 48 |
"Every nonfree program has a lord, a master -- |
| 49 |
and if you use the program, he is your master." Richard Stallman |
Archives