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