1 |
On 04/16/2012 11:11 AM, Michał Górny wrote: |
2 |
> On Tue, 10 Apr 2012 09:12:16 +0200 |
3 |
> ""Paweł Hajdan, Jr.""<phajdan.jr@g.o> wrote: |
4 |
> |
5 |
>> On 4/10/12 8:58 AM, Pacho Ramos wrote: |
6 |
>>> Other option would be to enable "wxwidgets" by default for that |
7 |
>>> profiles. |
8 |
>> |
9 |
>> I prefer this. Changing USE flag meaning in a counter-intuitive way |
10 |
>> (to let "gtk" mean "wxwidgets") would seem frustrating to me. |
11 |
>> |
12 |
>> With "wxwidgets" enabled by default people will get the most likely |
13 |
>> desired result (i.e. GUI) "out of the box", and setting |
14 |
>> USE="-wxwidgets" will have desired effect. |
15 |
>> |
16 |
>> Note that with USE="gtk" really meaning USE="wxwidgets", -wxwidgets |
17 |
>> would have no effect on such a package, which is the potentially |
18 |
>> surprising behavior I mentioned earlier. |
19 |
> |
20 |
> On the other hand, we should ask ourselves whether the USE flags are |
21 |
> very intuitive right now. |
22 |
> |
23 |
> Say, we have USE=ssl which enables SSL support. We already agreed |
24 |
> that's the correct meaning of it, and USE=gnutls,openssl,nss are just |
25 |
> to be used when there's more than one implementation to choose from. |
26 |
|
27 |
USE=ssl is also meaning OpenSSL and there should be no USE=openssl |
28 |
> |
29 |
> Shouldn't we have USE=gui in a similar fashion? Most of the devs |
30 |
> probably prefer the way 'I want GUI only if it's using my favorite |
31 |
> toolkit'. But users OTOH may prefer saying 'I want GUI in this app, no |
32 |
> matter what it uses'. |
33 |
> |
34 |
> This would probably handle the wxwidgets case most correct, having it |
35 |
> under USE=gui or similar. |
36 |
> |
37 |
|
38 |
-1, this would only add inconsistency / complexity to tree with packages |
39 |
having multiple graphical toolkits to pick from |
40 |
|
41 |
should be kept the way it is |
42 |
|
43 |
- Samuli |