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