1 |
On 02/08/2010 02:12 PM, Nikos Chantziaras wrote: |
2 |
> On 02/08/2010 01:36 PM, AllenJB wrote: |
3 |
>> On 08/02/10 11:15, Nikos Chantziaras wrote: |
4 |
>>> Hello. Please don't be too harsh if I got this wrong or if this looks |
5 |
>>> like whining :P |
6 |
>>> |
7 |
>>> A lot of ebuilds seem to ignore the "X" USE flag and instead only have |
8 |
>>> "gtk", "qt" and the like. This should be declared absolutely wrong, |
9 |
>>> IMHO. When a program provides a command-line tool and a GUI tool, and |
10 |
>>> the GUI tool uses only one toolkit, then the USE flag should be "X". |
11 |
>>> [...] |
12 |
>>> |
13 |
>> I don't see that either system makes particularly more sense than the |
14 |
>> other. |
15 |
>> |
16 |
>> The only situation that comes immediately to mind is: Under the current |
17 |
>> system, if packages add or remove support for multiple toolkits, the |
18 |
>> changes are trivial, but under your system it would invoke shuffling use |
19 |
>> flags around (which could easily affect dependencies in other packages). |
20 |
>> It would also not be immediately clear which toolkits support has been |
21 |
>> added/removed under the proposed system (since a package would go from, |
22 |
>> for example, having use flags "gtk kde" to just "X"). |
23 |
> |
24 |
> If it would be problematic for a package to switch to "X" then of course |
25 |
> it might be better to leave it as-is. But most of the time, the |
26 |
> programs in question only state "gtk" or "fltk" in them, even though Gtk |
27 |
> is not optional at all. A perfect example here is media-video/xvattr. |
28 |
> If you don't set the "gtk" USE flag, then you don't get the graphical |
29 |
> tool at all, only the command line tool. |
30 |
|
31 |
Very bad example. |
32 |
|
33 |
That's what people want: xvattr is used on headless VDR multimedia |
34 |
HTPC's, and VDR doesn't need toolkits like GTK+ installed. |