| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 08/11/2015 03:41 AM, Sergey Popov wrote: |
| 5 |
> I'd suggest to make a QA team meeting to override this policies |
| 6 |
> with more correct and rationale. |
| 7 |
> |
| 8 |
> Qt team members are greatly appreciated on this meeting. Even more, |
| 9 |
> i think that we should not take any decision on this without at |
| 10 |
> least Qt team lead(or half of Qt team devs) |
| 11 |
> |
| 12 |
> So, let's arrange some time and talk about this, cause it is |
| 13 |
> really confusing. Qt team point is understandable, but it's still |
| 14 |
> wrong. Let's make some consensus here. |
| 15 |
> |
| 16 |
> 02.08.2015 19:34, Ben de Groot пишет: |
| 17 |
>> Recently some team members of the Qt project have adopted these |
| 18 |
>> ebuild policies: |
| 19 |
>> https://wiki.gentoo.org/wiki/Project:Qt/Policies |
| 20 |
>> |
| 21 |
>> I have an issue with the policy adopted under "Requires one of |
| 22 |
>> two Qt versions". In my opinion, in the case where a package |
| 23 |
>> offers a choice between qt4 or qt5, we should express this in |
| 24 |
>> explicit useflags and a REQUIRED_USE="^^ ( qt4 qt5 )". This |
| 25 |
>> offers the user the clearest choice. |
| 26 |
>> |
| 27 |
>> Other developers state that users are not interested in such |
| 28 |
>> implementation details, or that forced choice through |
| 29 |
>> REQUIRED_USE is too much of a hassle. This results in current |
| 30 |
>> ebuilds such as quassel to not make it clear that qt4 is an |
| 31 |
>> option. |
| 32 |
>> |
| 33 |
>> This goes against the principle of least surprise, as well as |
| 34 |
>> against QA recommendations. I would like to hear specifically |
| 35 |
>> from QA about how we should proceed, but comments from the wider |
| 36 |
>> developer community are also welcome. |
| 37 |
>> |
| 38 |
>> -- Cheers, |
| 39 |
>> |
| 40 |
>> Ben | yngwin Gentoo developer |
| 41 |
>> |
| 42 |
> |
| 43 |
> |
| 44 |
I'm interested in this meeting as well, as maintainer of a package |
| 45 |
that can be built with one of two toolkit versions. At the moment, I'm |
| 46 |
using REQUIRED_USE with a preference preset for users that don't care, |
| 47 |
but it does cause a problem when both flags are set (so it's something |
| 48 |
I'd like to fix). I'd like to be part of the conversation if you don't |
| 49 |
mind. |
| 50 |
|
| 51 |
- -- |
| 52 |
Daniel Campbell - Gentoo Developer |
| 53 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 54 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
| 55 |
-----BEGIN PGP SIGNATURE----- |
| 56 |
Version: GnuPG v2 |
| 57 |
|
| 58 |
iQIcBAEBCAAGBQJVykQPAAoJEAEkDpRQOeFwVAgP+wYqVva9YHWmUOwC2dyrUFhx |
| 59 |
EjnPHBRaAsd6vOdoKKoFbO2c4wMhcoXb2C9pgLDw4O+eB2Q7JE3iMiiG/vAwGGtN |
| 60 |
10meoAjvFV+DxpB7EYiHNj8NtlKq8PAncHusu6H/eP7YwdS37ruO4E89nBbXzxjU |
| 61 |
JQru2bxL6Jf7m/LuI5lihdU6fwe1GrsDz0fCaeZ/49zBE8EPY1PjDbV8G8vHq/S6 |
| 62 |
UAgGXmFbzN8lPXfgBgnaD4O6So+WrhILUeTy4CVUQu0599W4UFmLqOmupeRHD0SM |
| 63 |
wHjtJ/0gW+Wfb7VbuQsfrmNYuu0Fh/Wx15qs62/8YcgIOxb5YI31cefPa7e3HZbm |
| 64 |
RQ52JC16Pl7VxPEsf5jhcQ6+QCpdOi/jH7B72JQiSgmtLF9N6j4kcr8XGtJB/HLy |
| 65 |
PlJES1865ugS8LWpMiJCCwGyO8o/lOi4scbumw+XxjWj43Z93d66wGK84Yf2goAL |
| 66 |
VBVA0JjzrJ46EIrBbqOPECMZZvJjeq4t28V3DHAdLPZmxhvLQjIjEqb8wywR5USa |
| 67 |
NJ4kDgP5H85udznBk7JWapFu+ipphFm8uzKt6nqCeAfVc/y3n4rLZ9aUDCBVKodv |
| 68 |
lzr652TmUw2sBvmhM6oRqsGZuMg6t0peBOOTFjTMJl+WYG+eUybvsWk9RQ9HQpuW |
| 69 |
aqpPa6GiLL9Gbx8JTX8F |
| 70 |
=JOKI |
| 71 |
-----END PGP SIGNATURE----- |
Archives