| 1 |
On June 1, 2016 7:29:55 AM PDT, Mart Raudsepp <leio@g.o> wrote: |
| 2 |
>Hello, |
| 3 |
> |
| 4 |
>So here's something more simple wrt GUI USE flags. |
| 5 |
> |
| 6 |
>Global USE=gui for |
| 7 |
>gui - enable an optional graphics user interface or extra GUI tool |
| 8 |
> |
| 9 |
>(wording improvements welcome, once it's in principle agreed; but no |
| 10 |
>point in bikeshed painting description wording till it is) |
| 11 |
> |
| 12 |
>Local USE flag description overrides to specify exactly what extra tool |
| 13 |
>is built and installed with the flag are encouraged. |
| 14 |
> |
| 15 |
> |
| 16 |
>This is meant to cover the cases where a package has an optional GUI, |
| 17 |
>as a user facing graphical application, whichever the toolkit. |
| 18 |
> |
| 19 |
>It is meant as a feature based USE flag, as opposed to the "extra dep" |
| 20 |
>based USE flags we've been using for this. |
| 21 |
>There are a lot of those with USE=gtk right now. In many cases it's |
| 22 |
>some little add-on graphical utility for a library, or some graphical |
| 23 |
>configuration GUI in addition to command line, or some bigger cases in |
| 24 |
>more modular packages that provide multiple frontends, and not all of |
| 25 |
>them are graphical, but CLI or TUI (TUI meaning ncurses-based or |
| 26 |
>similar). |
| 27 |
>Also there are various with USE=X where it's also about that, but X |
| 28 |
>isn't the only way to do GUI these days (any gtk3 app that doesn't |
| 29 |
>directly use libX11/libxcb/etc themselves natively supports wayland, |
| 30 |
>for example). |
| 31 |
> |
| 32 |
>Essentially, if it's an optional GUI, it'd be behind a USE=gui, instead |
| 33 |
>of USE=gtk, USE=X, USE=qt4 or USE=qt5, when that optional GUI is |
| 34 |
>available in only one toolkit version. So hence feature based flag, not |
| 35 |
>dependency-based. |
| 36 |
> |
| 37 |
>http://tinyurl.com/gtk-use was an old analysis of USE=gtk usage in tree |
| 38 |
>by Gilles over a year ago. That suggests that at least 80+ USE flags |
| 39 |
>should be then USE=gui instead of USE=gtk out of that analyzed USE=gtk |
| 40 |
>subset alone, not counting USE=X and others. |
| 41 |
> |
| 42 |
>There are some other things in the ideas pipeline for when there are |
| 43 |
>multiple toolkit choices, but that's something for a different thread, |
| 44 |
>a different day and more controversial. |
| 45 |
> |
| 46 |
> |
| 47 |
>Mart |
| 48 |
|
| 49 |
This idea is solid imo, but only in the case where there's a single (optional) GUI to use. We've discussed the finer points of this on IRC and, as you noted, the specifics need some more input and refinement, but in essence I like and support this idea. |
| 50 |
-- |
| 51 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Archives