1 |
Willie Wong <wwong <at> math.princeton.edu> writes: |
2 |
|
3 |
|
4 |
> > It makes gcc-4.5.3 use a newer method to detect parallelism, thus |
5 |
> > (potentially) makes programs compiled by gcc to have better multithreaded |
6 |
> > performance. |
7 |
|
8 |
> Now, why can't the USE descriptions be like the kernel option |
9 |
> descriptions and have something like what Pandu wrote included? |
10 |
|
11 |
I added this to root's .bashrc a long time ago: |
12 |
|
13 |
# USE flag settings hack by Ciaran McCreesh: |
14 |
explainuseflag(){ sed -ne "s,^\([^ ]*:\)\?$1 - ,,p" $(portageq |
15 |
portdir)/profiles/use.{,local.}desc; } |
16 |
alias ef="explainuseflag" |
17 |
|
18 |
|
19 |
Then simply use the alias for a quick check to learn about all the different |
20 |
uses of a given flag: |
21 |
|
22 |
'ef graphite' |
23 |
|
24 |
# ef graphite |
25 |
Enable support for non-Roman fonts via media-gfx/graphite2 |
26 |
Enable support for non-Roman fonts via media-gfx/graphite2 |
27 |
Add support for the framework for loop optimizations based on a polyhedral |
28 |
intermediate representation |
29 |
|
30 |
Then drill down into the a specific package's use flag meaning, using the |
31 |
aforementioned 'equery u' delineated by Albert. |
32 |
|
33 |
hth, |
34 |
|
35 |
James |