From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: USE flags in virtuals, to allow a specific provider to be determined
Date: Fri, 25 Jul 2014 16:23:23 -0500 [thread overview]
Message-ID: <20140725212323.GA5842@linux1> (raw)
In-Reply-To: <53D2B60D.3040402@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
On Fri, Jul 25, 2014 at 03:54:53PM -0400, Ian Stakenvicius wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 25/07/14 03:51 PM, Pacho Ramos wrote:
> > El vie, 25-07-2014 a las 20:46 +0100, Ciaran McCreesh escribió:
> >> On Fri, 25 Jul 2014 21:44:02 +0200 Luis Ressel <aranea@aixah.de>
> >> wrote:
> >>> Okay, I didn't think of that. I'm not sure if the blocker deps
> >>> or the REQUIRED_USE would be more helpful for Portage, but
> >>> generally I think that the REQUIRED_USE error message is quite
> >>> hard to understand for unexperienced users -- much more so than
> >>> the error generated by a blocker dep.
> >>
> >> ...and the fix for that is to scrap REQUIRED_USE and use
> >> pkg_pretend instead.
> >>
> >
> > Could you give an example to let us see how pkg_pretend could be
> > used to achieve the same as REQUIRED_USE?
> >
> > Thanks
> >
> >
>
> pkg_pretend() {
> if use heimdal && use mit-krb5; then
> eerror "Please set only one of the use following flags:"
> eerror "heimdal, mit-krb5"
> die "conflicting use flags set"
> fi
> }
I think this could get complicated really quick though.
For example, if I have an ebuild with three use flags,
flag1/flag2/flag3 with the requirement that one and only one of them
must be set, unless bash has an xor operator I don't know about, that
is going to need a lot of nesting etc to get right.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2014-07-25 21:23 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 18:49 [gentoo-dev] RFC: USE flags in virtuals, to allow a specific provider to be determined Ian Stakenvicius
2014-07-25 19:04 ` Luis Ressel
2014-07-25 19:23 ` Ian Stakenvicius
2014-07-25 19:44 ` Luis Ressel
2014-07-25 19:46 ` Ciaran McCreesh
2014-07-25 19:49 ` Ian Stakenvicius
2014-07-25 19:51 ` Pacho Ramos
2014-07-25 19:54 ` Ian Stakenvicius
2014-07-25 20:12 ` Pacho Ramos
2014-07-25 20:18 ` Ciaran McCreesh
2014-07-26 8:28 ` Pacho Ramos
2014-07-25 21:13 ` Ian Stakenvicius
2014-07-25 21:25 ` Ciaran McCreesh
2014-07-25 21:23 ` William Hubbs [this message]
2014-07-25 21:25 ` Ciaran McCreesh
2014-07-25 21:46 ` William Hubbs
2014-07-25 21:50 ` Ciaran McCreesh
2014-07-26 17:45 ` [gentoo-dev] " Jonathan Callen
2014-07-27 15:38 ` William Hubbs
2014-07-25 20:41 ` [gentoo-dev] " Michał Górny
2014-07-25 21:09 ` Ian Stakenvicius
2014-07-26 7:17 ` justin
2014-07-26 8:05 ` [gentoo-dev] " Duncan
2014-07-26 8:30 ` Pacho Ramos
2014-07-26 8:53 ` Michał Górny
2014-07-26 9:01 ` Duncan
2014-07-26 12:46 ` Ciaran McCreesh
2014-07-26 8:58 ` Duncan
2014-07-26 13:31 ` Ian Stakenvicius
2014-07-26 14:40 ` [gentoo-dev] " Manuel Rüger
2014-07-27 17:11 ` Peter Stuge
2014-07-28 14:20 ` Ian Stakenvicius
2014-07-28 14:42 ` Michał Górny
2014-07-28 15:11 ` Ian Stakenvicius
2014-07-28 11:21 ` Michał Górny
2014-07-28 17:02 ` Ian Stakenvicius
2014-07-29 4:23 ` James Potts
2014-07-29 11:06 ` Ciaran McCreesh
2014-07-29 4:51 ` 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=20140725212323.GA5842@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.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