| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 05/07/2012 08:50 PM, Michał Górny wrote: |
| 5 |
> On Mon, 07 May 2012 14:41:33 -0700 Zac Medico <zmedico@g.o> |
| 6 |
> wrote: |
| 7 |
> |
| 8 |
>> On 05/07/2012 01:43 PM, Michał Górny wrote: |
| 9 |
>>> On Mon, 07 May 2012 13:24:31 -0700 Zac Medico |
| 10 |
>>> <zmedico@g.o> wrote: |
| 11 |
>>> |
| 12 |
>>>> On 05/07/2012 12:18 PM, Ulrich Mueller wrote: |
| 13 |
>>>>>>>>>> On Mon, 7 May 2012, Ciaran McCreesh wrote: |
| 14 |
>>>>> |
| 15 |
>>>>>> I propose: |
| 16 |
>>>>> |
| 17 |
>>>>>> REQUIRED_USE="== ( qt webkit )" |
| 18 |
>>>>> |
| 19 |
>>>>> But this just means that the ebuild has redundant USE |
| 20 |
>>>>> flags, so one of them shouldn't be in IUSE, in the first |
| 21 |
>>>>> place. |
| 22 |
>>>> |
| 23 |
>>>> It serves to convey meaning, such that a user who has |
| 24 |
>>>> disabled the qt USE flag will get a meaningful prompt if that |
| 25 |
>>>> flag is required for webkit support. This kind of information |
| 26 |
>>>> could be useful to some people, and it may be preferable to |
| 27 |
>>>> having a separate webkit-qt flag. |
| 28 |
>>> |
| 29 |
>>> If 'qt' flag is required for webkit support, it's 'webkit? ( qt |
| 30 |
>>> )'. |
| 31 |
>> |
| 32 |
>> What if '!webkit? ( !qt )' also applies though? As an alternative |
| 33 |
>> to listing both constraints separately, you could combine them as |
| 34 |
>> '^^ ( webkit !qt )', or add support for '== ( qt webkit )' to |
| 35 |
>> make the expression easier to read. |
| 36 |
> |
| 37 |
> Then it's pointless to have the 'webkit' flag which doesn't |
| 38 |
> control anything. |
| 39 |
|
| 40 |
Generalize the discussion to be about two abstract flags "x" and "y" |
| 41 |
that have the same kind of relationship, where each one actually does |
| 42 |
control something, but the two features are intertwined in a |
| 43 |
particular package such that they must both be enabled or disabled in |
| 44 |
unison. |
| 45 |
- -- |
| 46 |
Thanks, |
| 47 |
Zac |
| 48 |
-----BEGIN PGP SIGNATURE----- |
| 49 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 50 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 51 |
|
| 52 |
iEYEARECAAYFAk+omdkACgkQ/ejvha5XGaO4CQCdGwcuuk4usnDj25nrcmd7D697 |
| 53 |
/TgAn3vXcPzEX3jCLhBVPPbnnX+lLWDW |
| 54 |
=G/eD |
| 55 |
-----END PGP SIGNATURE----- |
Archives