1 |
2011/3/31 Eray Aslan <eras@g.o>: |
2 |
> On Wed, Mar 30, 2011 at 04:41:25PM -0500, Dale wrote: |
3 |
>> +1 Some descriptions may as well not have one at all. May as well |
4 |
>> Google the flag and the package and see what, if anything, it returns. |
5 |
> |
6 |
> I would say working as intended. If you do not know what a package |
7 |
> does, chances are you don't need to enable it. And if you do want |
8 |
> to tinker, USE flags gives you enough of a hint to start googling. |
9 |
|
10 |
This has nothing to do with what you want to imply here. It's not |
11 |
about the tech skill of the user reading the definition. It's about |
12 |
the definitions being generic and vague enough so they can fit eight |
13 |
thousand packages that doesn't relate in any way, right? |
14 |
|
15 |
To say that the kde use flag gives "support for kde" says next to |
16 |
nothing to me on some packages. When I look into the ebuild and/or |
17 |
into the sources I can see all it does is to copy a .desktop file |
18 |
somewhere, or to enable the kde file dialog, or to create a window |
19 |
deco or a plasma snippet, or a phonon backend, or a color scheme. |
20 |
That's what I wanted to know and there's no way I can know it by |
21 |
looking at the USE description. |
22 |
|
23 |
> Having said that, we should at least have gramatically correct |
24 |
> English in descriptions. One might also lean towards more verbosity |
25 |
> in end-user oriented packages (versus server/backend/toolchain |
26 |
> packages). In any case, 10-15 words should be more than enough to |
27 |
> explain what a USE flag does. |
28 |
|
29 |
Mostly. But try cleaning the ffmpeg/libav-mplayer mess to decide which |
30 |
codec to use and you will find that a clear explanation (so you can |
31 |
decide) can't fit into that space. |
32 |
|
33 |
I don't have a problem reading ebuilds, though having to dive into the |
34 |
sources of a big package is another story, but I can understand users |
35 |
that find this an unpractical "solution". After all, if the USE |
36 |
descriptions doesn't tell a thing we should just remove them because |
37 |
they are taking space in our portage tree to provide zero info. So, |
38 |
"kde" flag purpose is to "enable support for KDE", oh, |
39 |
really?[/sarcasm] |
40 |
|
41 |
-- |
42 |
Jesús Guerrero Botella |