1 |
David Juhl posted on Sun, 30 Aug 2009 10:59:23 -0500 as excerpted: |
2 |
|
3 |
> Is there a simpler way to find out the use flags for a complete desktop |
4 |
> environment? I have gnome working. But what I can't answer is what I |
5 |
> don't have working. I wouldn't know where to begin to look. Maybe I am |
6 |
> missing something due to my ignorance... Maybe it doesn't matter |
7 |
> because what I have works... Maybe it does because I can do something |
8 |
> in the gui as opposed to the cli... |
9 |
> |
10 |
> If someone could give me some thoughts on the matter it'd be greatly |
11 |
> appreciated. |
12 |
|
13 |
Well, it all depends on what your definition of "complete" is. =:^) |
14 |
|
15 |
Generally speaking, if you're using a desktop profile, all the most sane |
16 |
USE flags you need are set there by default. Where individual packages |
17 |
differ from the norm, there's per-package USE flag defaults now, and the |
18 |
Gentoo package again decides what's the most sane setting for most users, |
19 |
and sets the defaults accordingly. Of course, the defaults don't apply |
20 |
if you've set the USE flag yourself, overruling them. either globally, or |
21 |
in package.use for individual packages. But the defaults should be sane |
22 |
for someone who doesn't want to be bothered by too much detail. |
23 |
|
24 |
If your definition of "complete" is "every feature possible", or if |
25 |
you're a detail person, or a control freak when it comes to what's |
26 |
running on your computer (as I most certainly am), the defaults aren't |
27 |
going to satisfy you. Of course, the "every feature possible" bit is |
28 |
generally fairly easy, just check your emerge --verbose --pretend output, |
29 |
and enable nearly everything (except for the few no-feature type flags) |
30 |
you see in make.conf. |
31 |
|
32 |
If you're a control freak or detail person, euse, from the gentoolkit |
33 |
package, is very helpful. Again, check the output of emerge --pretend |
34 |
--verbose, and for new packages or whenever a flag change comes up, check |
35 |
it. If you don't know what that USE flag does, a quick euse -i <flag> |
36 |
gives you the descriptions, both global and per-package, if they exist, |
37 |
along with whether the flag is enabled and where it's set (profile |
38 |
default, make.conf, etc). |
39 |
|
40 |
Of course, the /really/ detail oriented control freaks won't be satisfied |
41 |
with that either, as the USE flag descriptions tend to be rather vague, |
42 |
particularly in regard to how individual packages use them. These types |
43 |
of people will be grepping the ebuild itself for this information, seeing |
44 |
whether it simply turns on dependencies for other packages, or does |
45 |
something else. |
46 |
|
47 |
-- |
48 |
Duncan - List replies preferred. No HTML msgs. |
49 |
"Every nonfree program has a lord, a master -- |
50 |
and if you use the program, he is your master." Richard Stallman |