1 |
On 08/02/10 11:15, Nikos Chantziaras wrote: |
2 |
> Hello. Please don't be too harsh if I got this wrong or if this looks |
3 |
> like whining :P |
4 |
> |
5 |
> A lot of ebuilds seem to ignore the "X" USE flag and instead only have |
6 |
> "gtk", "qt" and the like. This should be declared absolutely wrong, |
7 |
> IMHO. When a program provides a command-line tool and a GUI tool, and |
8 |
> the GUI tool uses only one toolkit, then the USE flag should be "X". |
9 |
> "gtk" vs "qt" vs "fltk" etc should be used only in cases where a program |
10 |
> can be built with either of those toolkits. When there's only one |
11 |
> choice, then this doesn't make sense. Isn't this what the "X" USE flag |
12 |
> is there for in the first place? Having a package where, say, Gtk is |
13 |
> *not* optional having a "gtk" USE flag doesn't make sense. The X tool |
14 |
> of that package is optional, but Gtk is not optional for the X tool. |
15 |
> |
16 |
> A Gnome user probably has "X gtk -qt" in make.conf, while a KDE user has |
17 |
> "X qt -gtk" in hope to have programs that support both Gtk and Qt being |
18 |
> built with the toolkit that is more native to his DE. When a package |
19 |
> has a GUI tool that is able to only use one of those toolkits, people |
20 |
> who have it disabled in make.conf will get no GUI tool at all even |
21 |
> though they have "X" in their USE flags. |
22 |
> |
23 |
> I hope I was able to explain the problem (as I see it) correctly :P If |
24 |
> people agree with me, it might be a good idea for maintainers of |
25 |
> packages that behave like that to start using "X" as the USE flag that |
26 |
> controls building of the packages GUI tools. |
27 |
> |
28 |
> |
29 |
I don't see that either system makes particularly more sense than the |
30 |
other. |
31 |
|
32 |
The only situation that comes immediately to mind is: Under the current |
33 |
system, if packages add or remove support for multiple toolkits, the |
34 |
changes are trivial, but under your system it would invoke shuffling use |
35 |
flags around (which could easily affect dependencies in other packages). |
36 |
It would also not be immediately clear which toolkits support has been |
37 |
added/removed under the proposed system (since a package would go from, |
38 |
for example, having use flags "gtk kde" to just "X"). |
39 |
|
40 |
Of course, even if your system was saner, the ultimate question is: |
41 |
Who's going to run through all the graphical packages and update all the |
42 |
use flags and dependencies? |
43 |
|
44 |
AllenJB |