From: Alex Alexander <wired@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pkg_pretend USE validation and VALID_USE alternative
Date: Wed, 31 Mar 2010 20:49:26 +0300 [thread overview]
Message-ID: <20100331174925.GA16267@faith> (raw)
In-Reply-To: <20100331092035.GA11663@hrair>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On Wed, Mar 31, 2010 at 02:20:35AM -0700, Brian Harring wrote:
> Hola all-
>
> For those who aren't familiar, pkg_pretend is in EAPI4- the main usage
> of it is will be use dep checking- this email is specifically
> regarding an alternative to it that *should* be superior for that use
> case, but I'm looking for feedback.
>
> Basically, we use the original VALID_USE proposal from way back in
> '05- if you're familiar w/ MYOPTIONS, they're reasonably similar.
>
> Roughly, VALID_USE is a list of constraints stating what the allowed
> use flag combinations are for this pkg. If you think of normal
> depdencies (I must have openssl and python merged prior), it's the
> same machinery.
>
> [snip]
>
> Comments desired; assuming no significant blowback, I'll be pushing
> this to the council level since eapi4 is annoying feature locked right
> now.
I like the whole concept, it is clean and straightforward.
Also, notifying the user of any possible issues and breaking so he can
make the actual decision sounds far better than making the choice for him.
VALID_USE does look a bit strange.
how about
IUSE_RULES
or
IUSE_RESTRICTIOMS
or
RUSE
?
--
Alex Alexander :: wired
Gentoo Developer
www.linuxized.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-03-31 17:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:20 [gentoo-dev] pkg_pretend USE validation and VALID_USE alternative Brian Harring
2010-03-31 9:48 ` [gentoo-dev] Re: [gentoo-council] " Ulrich Mueller
2010-03-31 10:46 ` Brian Harring
2010-03-31 11:04 ` [gentoo-dev] " Ulrich Mueller
2010-03-31 11:11 ` Brian Harring
2010-03-31 15:38 ` "Paweł Hajdan, Jr."
2010-03-31 11:18 ` [gentoo-dev] Re: [gentoo-council] " Piotr Jaroszyński
2010-04-01 20:44 ` Róbert Čerňanský
2010-04-01 21:51 ` Zac Medico
[not found] ` <201003312316.23806.ali_bush@gentoo.org>
2010-03-31 10:57 ` Brian Harring
2010-03-31 17:49 ` Alex Alexander [this message]
2010-03-31 19:46 ` [gentoo-dev] " Brian Harring
2010-03-31 19:56 ` Ciaran McCreesh
2010-04-01 7:31 ` Brian Harring
2010-04-01 7:41 ` Ciaran McCreesh
2010-04-01 7:56 ` Brian Harring
2010-04-01 10:10 ` Gilles Dartiguelongue
2010-04-01 10:18 ` Brian Harring
2010-04-01 10:42 ` Gilles Dartiguelongue
2010-04-01 10:59 ` Brian Harring
2010-04-01 11:23 ` Ciaran McCreesh
2010-04-01 11:38 ` Brian Harring
2010-04-01 11:50 ` Ciaran McCreesh
2010-04-01 10:49 ` Ciaran McCreesh
2010-04-01 11:18 ` Brian Harring
2010-04-01 11:44 ` Ciaran McCreesh
2010-04-01 17:04 ` David Leverton
2010-04-01 18:39 ` Dror Levin
2010-04-01 18:55 ` Ciaran McCreesh
2010-04-02 22:36 ` David Leverton
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=20100331174925.GA16267@faith \
--to=wired@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