1 |
Hello. Please don't be too harsh if I got this wrong or if this looks |
2 |
like whining :P |
3 |
|
4 |
A lot of ebuilds seem to ignore the "X" USE flag and instead only have |
5 |
"gtk", "qt" and the like. This should be declared absolutely wrong, |
6 |
IMHO. When a program provides a command-line tool and a GUI tool, and |
7 |
the GUI tool uses only one toolkit, then the USE flag should be "X". |
8 |
"gtk" vs "qt" vs "fltk" etc should be used only in cases where a program |
9 |
can be built with either of those toolkits. When there's only one |
10 |
choice, then this doesn't make sense. Isn't this what the "X" USE flag |
11 |
is there for in the first place? Having a package where, say, Gtk is |
12 |
*not* optional having a "gtk" USE flag doesn't make sense. The X tool |
13 |
of that package is optional, but Gtk is not optional for the X tool. |
14 |
|
15 |
A Gnome user probably has "X gtk -qt" in make.conf, while a KDE user has |
16 |
"X qt -gtk" in hope to have programs that support both Gtk and Qt being |
17 |
built with the toolkit that is more native to his DE. When a package |
18 |
has a GUI tool that is able to only use one of those toolkits, people |
19 |
who have it disabled in make.conf will get no GUI tool at all even |
20 |
though they have "X" in their USE flags. |
21 |
|
22 |
I hope I was able to explain the problem (as I see it) correctly :P If |
23 |
people agree with me, it might be a good idea for maintainers of |
24 |
packages that behave like that to start using "X" as the USE flag that |
25 |
controls building of the packages GUI tools. |