From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] EAPI 7 in Portage needs YOU!
Date: Mon, 19 Feb 2018 11:58:01 -0800 [thread overview]
Message-ID: <8d91a537-9eed-e8ae-10af-1a7950a5e119@gentoo.org> (raw)
In-Reply-To: <1519069121.1104.9.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1383 bytes --]
On 02/19/2018 11:38 AM, Michał Górny wrote:
> W dniu pon, 19.02.2018 o godzinie 21∶32 +0200, użytkownik Mart Raudsepp
> napisał:
>> On Mon, 2018-02-19 at 18:34 +0100, Ulrich Mueller wrote:
>>>>>>>> On Mon, 19 Feb 2018, Michael Lienhardt wrote:
>>>>>
>>>>> 2. ||= (binding any-of) dep groups.
>>>>
>>>> I don't understand what this group means, and the PMS-7 is unclear
>>>> as well:
>>>> "binding-any-of A binding-any-of group, which has the same format
>>>> as the any-of group, but begins with the string ||= instead."
>>>> Is it a "or", like the "any-of" group, but with a different
>>>> behavior
>>>> at compiling/linking time?
>>>
>>> It is explained in section 8.2.4:
>>> https://dev.gentoo.org/~ulm/pms/7-draft/pms.html#x1-800008.2.4
>>
>> Maybe I missed this, but a real world use case example would be nice,
>> maybe someone feels a harder itch to scratch then :)
>>
>
> The original use case was for providers-like thingies, e.g.:
>
> ||= ( ffmpeg:0= libav:0= )
>
> That said, I'd personally prefer doing that with proper USE_EXPAND
> and REQUIRED_USE enforcing but this has been rejected.
Indeed, the tendency of || deps to make things less deterministic can be
troublesome. Maybe automatic REQUIRED_USE satisfaction will make the
REQUIRED_USE approach more acceptable to those who have rejected it.
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 224 bytes --]
next prev parent reply other threads:[~2018-02-19 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 10:49 [gentoo-dev] EAPI 7 in Portage needs YOU! Michał Górny
2018-02-19 11:00 ` Anthony G. Basile
2018-02-19 11:14 ` Luigi Mantellini
2018-02-19 15:15 ` Michał Górny
2018-02-19 17:07 ` Michael Lienhardt
2018-02-19 17:34 ` Ulrich Mueller
2018-02-19 19:32 ` Mart Raudsepp
2018-02-19 19:38 ` Michał Górny
2018-02-19 19:58 ` Zac Medico [this message]
2018-02-20 0:19 ` Michael Lienhardt
2018-02-20 2:45 ` Ian Stakenvicius
2018-02-20 2:30 ` Ian Stakenvicius
2018-02-20 4:31 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8d91a537-9eed-e8ae-10af-1a7950a5e119@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox