1 |
On 06/01/2016 10:29 AM, Mart Raudsepp 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 |
> Essentially, if it's an optional GUI, it'd be behind a USE=gui, instead |
10 |
> of USE=gtk, USE=X, USE=qt4 or USE=qt5, when that optional GUI is |
11 |
> available in only one toolkit version. So hence feature based flag, not |
12 |
> dependency-based. |
13 |
> |
14 |
I know that it was previously mentioned that there was discussion about |
15 |
this long ago, but I'm not familiar with those discussions. Is someone |
16 |
more familiar with those discussions able to bring up the talking points? |
17 |
|
18 |
One issue that springs to mind though is, let's say a pkg supports only |
19 |
qt4 for a gui, you'd have the gui flag. Upstream adds qt5 support. Do |
20 |
you keep the gui flag and make qt4 and qt5 dependent on it, or do you |
21 |
remove the gui flag? I feel like the latter might lead to confusion, |
22 |
while the former suggests that the flag should be used more generally |
23 |
than just one toolkit/version being available. |
24 |
> |
25 |
> Mart |
26 |
> |
27 |
|
28 |
-- |
29 |
NP-Hardass |