| 1 |
Rich Freeman posted on Fri, 11 Sep 2015 08:13:48 -0400 as excerpted: |
| 2 |
|
| 3 |
> USE=gui or something like that if the main effect is to have a gui or |
| 4 |
> not. |
| 5 |
> That is the sort of thing that SHOULD go in make.conf or in a profile. |
| 6 |
> If disabling gtk makes it a console-only application then use the gui |
| 7 |
> flag. |
| 8 |
|
| 9 |
I like the general proposal, but since it's going to council, can we try |
| 10 |
to kill another bird with the same stone? This USE=gui helps... |
| 11 |
|
| 12 |
Wayland's coming, and to the extent that USE=X has previously indicated a |
| 13 |
GUI, much like USE=gtk and USE=qt indicating the same thing, we're going |
| 14 |
to have problems. |
| 15 |
|
| 16 |
Can we make USE=gui the generic policy for that, and deprecate more |
| 17 |
specific forms for choosing /any/ gui, so they can be used for choosing |
| 18 |
/which/ gui? |
| 19 |
|
| 20 |
Then of course ordain both X and wayland USE flags for choosing specific |
| 21 |
gui platform, like gtk and qt did at their level traditionally. |
| 22 |
|
| 23 |
The question then remains whether ncurses, etc, should be treated as a |
| 24 |
gui. Maybe make mention of that one way or the other in the policy as |
| 25 |
well. |
| 26 |
|
| 27 |
-- |
| 28 |
Duncan - List replies preferred. No HTML msgs. |
| 29 |
"Every nonfree program has a lord, a master -- |
| 30 |
and if you use the program, he is your master." Richard Stallman |
Archives