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