| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 08/02/2015 12:12 PM, Rich Freeman wrote: |
| 5 |
> On Sun, Aug 2, 2015 at 2:21 PM, Andrew Savchenko |
| 6 |
> <bircoph@g.o> wrote: |
| 7 |
>> |
| 8 |
>> This is a clean solution for developers and maintainers, but not |
| 9 |
>> for ordinary users — they will confused by "qt qt4 qt5": "what |
| 10 |
>> is 'qt', how is it different from 'qt4' and 'qt5'. What you are |
| 11 |
>> really doing is implementing second-level USE flags, while they |
| 12 |
>> were supposed to be linear. |
| 13 |
> |
| 14 |
> No argument that it isn't intuitive, but setting USE=qt and |
| 15 |
> forgetting about it certainly seems more user-friendly than setting |
| 16 |
> qt4/qt5 on individual packages and worrying about which is better |
| 17 |
> where. To some extent the current qt policy accomplishes this, but |
| 18 |
> it sacrifices control when users actually do want it. |
| 19 |
> |
| 20 |
> I'm a bit torn on the issue myself, but just telling users to set |
| 21 |
> USE=qt and forget about it unless you really care seems pretty |
| 22 |
> simple to me. The documentation for USE=qt4/qt5 could say "this is |
| 23 |
> an advanced setting for users who want to prefer the qt4 |
| 24 |
> implementation over others - set USE=qt if all you care about is qt |
| 25 |
> support." |
| 26 |
> |
| 27 |
I like this idea. USE=qt for all apps that optionally support or need |
| 28 |
it, qt4/qt5 for apps that support both. We can default to qt5 and |
| 29 |
users can still choose qt4 if they prefer it. |
| 30 |
|
| 31 |
- -- |
| 32 |
Daniel Campbell - Gentoo Developer |
| 33 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 34 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
| 35 |
-----BEGIN PGP SIGNATURE----- |
| 36 |
Version: GnuPG v2 |
| 37 |
|
| 38 |
iQIcBAEBCAAGBQJVvxjcAAoJEAEkDpRQOeFwbIsQAJeCSW9NHUFyXirEhh/pL7cP |
| 39 |
Vc5F6bgxZhJ1svHiCxMAQuFz5POG/yxjq6iAwjtCaDaWBDj/HbSDe69Pu0HBcCkK |
| 40 |
ezb2AJTtacvkWDxlJhH4H9m7QB3M9/XWlKlfMAhKnDEaSFS/yieR578LE1sNd2aF |
| 41 |
A9JditTliVqmRr3DYNvT4JlqGIBJyU43gR75gW2gHyWE0FTZ4Rv8k6DQHJuseFb6 |
| 42 |
OvWWrDCKZQZqLmLIvpvz1ksyXuFis8qqCPLws37awo56kjT8jDJ+kdulwFGdvxui |
| 43 |
zrau+MtufhDwehVsVKKe1j/6dhVnmOqlIZd3H7Pule9jFsH6AGRN4s2dL2bp9vqi |
| 44 |
WdmQI8B6eDvdUK0Il1+zd7V1Uq8DXIYpTlOYrUHtnAlyaT8ln7FqojSKODASZ/10 |
| 45 |
LkJQ9SLv7ej6nQLnkYe4F1FQqssPqGe4v2tAZcFVu2pYda3KCP7PJKT70oFtzwrQ |
| 46 |
76jVgp5Ryp/cbZrM2tOEcvb/3kTXDHDW2Wavh+VV7XwBmTvXoXqZas+eHMMtbyDJ |
| 47 |
1cofAFRvu6HWnITTg3ZPoiQbm5Sq4rjG7aUvkyUxIoC8YzhXdHOTBpaYaFe6nZ/f |
| 48 |
45e7lHq4iDsArmBn2BiF4kBKZh8I5xMY1/K10mC8/4emBS3NHbafOUKqujCCqLMj |
| 49 |
dhh/jF4gLzALPIDGXBRp |
| 50 |
=j7X5 |
| 51 |
-----END PGP SIGNATURE----- |
Archives