1 |
On 02/19/2018 11:38 AM, Michał Górny wrote: |
2 |
> W dniu pon, 19.02.2018 o godzinie 21∶32 +0200, użytkownik Mart Raudsepp |
3 |
> napisał: |
4 |
>> On Mon, 2018-02-19 at 18:34 +0100, Ulrich Mueller wrote: |
5 |
>>>>>>>> On Mon, 19 Feb 2018, Michael Lienhardt wrote: |
6 |
>>>>> |
7 |
>>>>> 2. ||= (binding any-of) dep groups. |
8 |
>>>> |
9 |
>>>> I don't understand what this group means, and the PMS-7 is unclear |
10 |
>>>> as well: |
11 |
>>>> "binding-any-of A binding-any-of group, which has the same format |
12 |
>>>> as the any-of group, but begins with the string ||= instead." |
13 |
>>>> Is it a "or", like the "any-of" group, but with a different |
14 |
>>>> behavior |
15 |
>>>> at compiling/linking time? |
16 |
>>> |
17 |
>>> It is explained in section 8.2.4: |
18 |
>>> https://dev.gentoo.org/~ulm/pms/7-draft/pms.html#x1-800008.2.4 |
19 |
>> |
20 |
>> Maybe I missed this, but a real world use case example would be nice, |
21 |
>> maybe someone feels a harder itch to scratch then :) |
22 |
>> |
23 |
> |
24 |
> The original use case was for providers-like thingies, e.g.: |
25 |
> |
26 |
> ||= ( ffmpeg:0= libav:0= ) |
27 |
> |
28 |
> That said, I'd personally prefer doing that with proper USE_EXPAND |
29 |
> and REQUIRED_USE enforcing but this has been rejected. |
30 |
|
31 |
Indeed, the tendency of || deps to make things less deterministic can be |
32 |
troublesome. Maybe automatic REQUIRED_USE satisfaction will make the |
33 |
REQUIRED_USE approach more acceptable to those who have rejected it. |
34 |
-- |
35 |
Thanks, |
36 |
Zac |