1 |
Eray Aslan wrote: |
2 |
> On Wed, Mar 30, 2011 at 04:41:25PM -0500, Dale wrote: |
3 |
> |
4 |
>> +1 Some descriptions may as well not have one at all. May as well |
5 |
>> Google the flag and the package and see what, if anything, it returns. |
6 |
>> |
7 |
> I would say working as intended. If you do not know what a package |
8 |
> does, chances are you don't need to enable it. And if you do want |
9 |
> to tinker, USE flags gives you enough of a hint to start googling. |
10 |
> |
11 |
> Having said that, we should at least have gramatically correct |
12 |
> English in descriptions. One might also lean towards more verbosity |
13 |
> in end-user oriented packages (versus server/backend/toolchain |
14 |
> packages). In any case, 10-15 words should be more than enough to |
15 |
> explain what a USE flag does. |
16 |
> |
17 |
> |
18 |
|
19 |
As was posted by another person, google usually points right back to the |
20 |
Gentoo docs which does not help. For me, most of the time, the |
21 |
descriptions don't help a bit, not even to tinker. So, given that, |
22 |
maybe working as intended but still not very helpful. Having USE foo to |
23 |
say it enables foo does not help much if you don't know what foo is. |
24 |
There are a lot of them that says that and it really goes without saying |
25 |
that it does that. If you enable a USE flag, of course it enables the |
26 |
flag. Question is, what the heck is the flag? What does it do? |
27 |
|
28 |
Maybe we need a USE flag for smoke. See if someone tinkers with it and |
29 |
blows up their rig. lol |
30 |
|
31 |
In all seriousness, this has been discussed before and it doesn't get |
32 |
any better. I'm not sure how to fix it either. The space for the |
33 |
description is limited. |
34 |
|
35 |
Dale |
36 |
|
37 |
:-) :-) |