1 |
On 02/08/2010 01:30 PM, Tomáš Chvátal wrote: |
2 |
> Dne 8.2.2010 12:15, Nikos Chantziaras napsal(a): |
3 |
>> Hello. Please don't be too harsh if I got this wrong or if this looks |
4 |
>> like whining :P |
5 |
> |
6 |
>> A lot of ebuilds seem to ignore the "X" USE flag and instead only have |
7 |
>> "gtk", "qt" and the like. This should be declared absolutely wrong, |
8 |
>> IMHO. When a program provides a command-line tool and a GUI tool, and |
9 |
>> the GUI tool uses only one toolkit, then the USE flag should be "X". |
10 |
>> "gtk" vs "qt" vs "fltk" etc should be used only in cases where a program |
11 |
>> can be built with either of those toolkits. When there's only one |
12 |
>> choice, then this doesn't make sense. Isn't this what the "X" USE flag |
13 |
>> is there for in the first place? Having a package where, say, Gtk is |
14 |
>> *not* optional having a "gtk" USE flag doesn't make sense. The X tool |
15 |
>> of that package is optional, but Gtk is not optional for the X tool. |
16 |
> |
17 |
>> A Gnome user probably has "X gtk -qt" in make.conf, while a KDE user has |
18 |
>> "X qt -gtk" in hope to have programs that support both Gtk and Qt being |
19 |
>> built with the toolkit that is more native to his DE. When a package |
20 |
>> has a GUI tool that is able to only use one of those toolkits, people |
21 |
>> who have it disabled in make.conf will get no GUI tool at all even |
22 |
>> though they have "X" in their USE flags. |
23 |
> |
24 |
>> I hope I was able to explain the problem (as I see it) correctly :P If |
25 |
>> people agree with me, it might be a good idea for maintainers of |
26 |
>> packages that behave like that to start using "X" as the USE flag that |
27 |
>> controls building of the packages GUI tools. |
28 |
> |
29 |
> |
30 |
> Sounds sane. For correct usage lately the mplayer ebuild was rewritten |
31 |
> this way. |
32 |
> |
33 |
> Might be good idea to open tracker for these and all bugs cced to it. So |
34 |
> interested persons can fix it. |
35 |
> |
36 |
> Note for maintainers: qa bugs are considered as issue when adding new |
37 |
> packages. In longer perspective it is good to have them fixed, but you |
38 |
> don't have to proactively fix old packages. Writing this before people |
39 |
> starts complaining we are again filling lots of bugs. |
40 |
> |
41 |
> @qa: any objections against me opening the tracker? |
42 |
> |
43 |
> To sum up the issue: |
44 |
> use X wrap all other widget useflags if there is CLI interface |
45 |
> available, so if user don't want X usage for package he just set -X and |
46 |
> rest widget flags don't matter at all. |
47 |
> |
48 |
> Tomas |
49 |
|
50 |
IMHO. USE="X" is for controlling X.org dependencies, not for avoiding |
51 |
everything that deps on them, so I disagree. |
52 |
|
53 |
MPlayer is a bad example here. The reason for writing it like that is |
54 |
all the flags enabled by default with +. |
55 |
|
56 |
-Samuli |