1 |
Andreas K. Huettel posted on Tue, 18 Nov 2014 00:05:03 +0100 as excerpted: |
2 |
|
3 |
|
4 |
> Message to users- if you want a minimum set of useflags, start from the |
5 |
> main default profile of your arch. That's what it is for. Everything |
6 |
> else, and you sure get to keep the pieces. |
7 |
|
8 |
But for no-multilib, there's still both far too many USE flags enabled by |
9 |
default, and far too much stuff in @system, once dependencies are |
10 |
included. |
11 |
|
12 |
So here I'm on about the only amd64-no-multilib profile available, but |
13 |
with all @system packages negated and with USE="-* ...". |
14 |
|
15 |
And you know what? It actually works very well! =:^) |
16 |
|
17 |
Tho obviously I was a reasonably mature gentoo user before I tried it, I |
18 |
already had my main system setup, and when I set USE=-* I did an emerge |
19 |
--verbose --pretend and looked at what flags on what packages would |
20 |
change, before deciding whether that was sane and what I wanted, or not, |
21 |
and setting specific flags either globally or per-package accordingly. |
22 |
|
23 |
Similarly with the @system package negation. Negate the list a few |
24 |
packages at a time and do an emerge --pretend --depclean and see what |
25 |
comes up. If it's sane, unmerge it. Else add it to the appropriate |
26 |
custom set that's covered by the world-sets file. |
27 |
|
28 |
Nothing really dangerous or insane about that, as long as you take it a |
29 |
step at a time using --pretend first, and don't let it /do/ anything |
30 |
insane -- make the necessary set and USE flag changes to prevent emerge |
31 |
trying to remove something critical, and /then/ let it have at it with |
32 |
the rest. |
33 |
|
34 |
Like I said, as could be expected with gentoo, which routinely takes into |
35 |
account that users /might/ have a good reason for not wanting the |
36 |
defaults, it actually works really well. =:^) |
37 |
|
38 |
|
39 |
Tho I actually appreciate the "you get to keep the pieces" aspect as |
40 |
well. Unlike many distros, gentoo actually respects the user and their |
41 |
right to decide enough to give them the /power/ to break the system, if |
42 |
they "drink and emerge", or similar foolish things. The guard rails are |
43 |
there and that's appreciated, but there's also unlocked gates (with clear |
44 |
warnings on them) thru those guard rails, because that's what gentoo is |
45 |
/about/. Sure, people can and do go thru those gates from time to time, |
46 |
but it's their responsibility to be appropriately roped up if they do, |
47 |
and if they can't do that and end up falling off the gentoo cliff and |
48 |
landing on arch or fedora (or even osx or ms windows!) instead, well, it |
49 |
was probably for the best. |
50 |
|
51 |
So let's keep the warnings there as they do warn the unwary, but also the |
52 |
unlocked gates thru those default-use railings. =:^) |
53 |
|
54 |
-- |
55 |
Duncan - List replies preferred. No HTML msgs. |
56 |
"Every nonfree program has a lord, a master -- |
57 |
and if you use the program, he is your master." Richard Stallman |