1 |
Il 19/02/2018 20:38, Michał Górny ha scritto: |
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 |
>>> It is explained in section 8.2.4: |
6 |
>>> https://dev.gentoo.org/~ulm/pms/7-draft/pms.html#x1-800008.2.4 |
7 |
>> |
8 |
>> Maybe I missed this, but a real world use case example would be nice, |
9 |
>> maybe someone feels a harder itch to scratch then :) |
10 |
>> |
11 |
> |
12 |
> The original use case was for providers-like thingies, e.g.: |
13 |
> |
14 |
> ||= ( ffmpeg:0= libav:0= ) |
15 |
> |
16 |
> That said, I'd personally prefer doing that with proper USE_EXPAND |
17 |
> and REQUIRED_USE enforcing but this has been rejected. |
18 |
> |
19 |
|
20 |
So, if I understand correctly, the ||= group is an "or" that must be resolved in the same way in the DEPEND and RDEPEND dependencies, right? |
21 |
|
22 |
The documentation does not specify how this group interacts between different ebuilds. |
23 |
I guess there is no interaction, but just to be sure, let consider the following corner-case example: |
24 |
- a package A has RDEPEND=||= ( ffmpeg:0= libav:0= ) while another package B has DEPEND=ffmpeg |
25 |
- the solver choose libav to solve the dependency of the first package and ffmpeg to solve the second, removing ffmpeg afterward |
26 |
- will package A break? |
27 |
|
28 |
Michael Lienhardt |