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