1 |
On Mon, May 23, 2011 at 12:27 PM, Dale <rdalek1967@×××××.com> wrote: |
2 |
> The reason the info is there is so that users, like me, know what the USE |
3 |
> flag is for. Me personally, I still think some of them don't help much and |
4 |
> need more info but it is better than it used to be. So, if you can make |
5 |
> them shorter and users still able to figure out what they do, great. If |
6 |
> not, then the info needs to stay. Us users need it. |
7 |
|
8 |
++ |
9 |
|
10 |
A description of USE=foo enables foo support is just about useless. |
11 |
Why even have the description at all in that case? |
12 |
|
13 |
What I want to know is whether I want foo support. A description of |
14 |
"Disables 99% of the functionality in chromium but still lets you |
15 |
parse the config files from a command line on an embedded system" lets |
16 |
me know that unless I'm doing something exotic it isn't for me. |
17 |
|
18 |
A long sentence is probably the right level of detail. Two sentences |
19 |
is probably warranted if messing with the flag can cause havoc. |
20 |
|
21 |
Rich |