From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libgphoto2-2.4.10 news item
Date: Mon, 14 Feb 2011 11:35:42 +0100 [thread overview]
Message-ID: <1297679742.7123.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20110213201709.019c46e4@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
El dom, 13-02-2011 a las 20:17 +0000, Ciaran McCreesh escribió:
> On Sun, 13 Feb 2011 21:00:31 +0100
> Pacho Ramos <pacho@gentoo.org> wrote:
> > If rest of gnome team agrees, I think we could go with, but I still
> > fail to see what is the "technical" problem on allowing CAMERAS="*"
> > to be used :-|
>
> 'cameras_*' isn't a valid use flag name, so the package mangler can't
> just pass the * through to the ebuild, which means it has to expand the
> value itself. But there's no complete list of every CAMERA value
> anywhere, so it can't.
>
> There were plans to fix this in EAPI 4 by requiring that IUSE be
> accurate. That would have allowed the package mangler to use IUSE to
> get a complete list of known CAMERAS and be able to expand * that way.
> Unfortunately, that feature got dropped, and so in EAPI 4 you're still
> allowed to make use of USE_EXPAND variables without making sure IUSE is
> complete.
>
Do you know if there are any plans on implementing it on a future EAPI?
I think being able to simply enable all of them with "*" would be
interesting (at least in the future)
Thanks for the information
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-14 10:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 17:03 [gentoo-dev] libgphoto2-2.4.10 news item Pacho Ramos
2011-02-13 17:09 ` Ciaran McCreesh
2011-02-13 17:16 ` Pacho Ramos
2011-02-13 19:31 ` Pacho Ramos
2011-02-13 19:34 ` Ciaran McCreesh
2011-02-13 20:00 ` Pacho Ramos
2011-02-13 20:17 ` Ciaran McCreesh
2011-02-14 9:07 ` [gentoo-dev] " Duncan
2011-02-14 13:17 ` Ciaran McCreesh
2011-02-14 10:35 ` Pacho Ramos [this message]
2011-02-14 13:21 ` [gentoo-dev] " Ciaran McCreesh
2011-02-13 20:00 ` Matthew Summers
2011-02-13 20:08 ` Pacho Ramos
2011-02-14 10:15 ` Pacho Ramos
2011-02-14 10:24 ` Gilles Dartiguelongue
2011-02-14 10:34 ` Pacho Ramos
2011-02-14 10:37 ` Gilles Dartiguelongue
2011-02-14 10:40 ` Pacho Ramos
2011-02-14 10:42 ` Pacho Ramos
2011-02-14 10:53 ` Gilles Dartiguelongue
2011-02-14 13:19 ` Ciaran McCreesh
2011-02-14 13:33 ` Pacho Ramos
2011-02-14 13:41 ` Ciaran McCreesh
2011-02-14 18:25 ` Pacho Ramos
2011-02-14 10:41 ` Ulrich Mueller
2011-02-14 10:53 ` Pacho Ramos
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=1297679742.7123.9.camel@localhost.localdomain \
--to=pacho@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