From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] vala.eclass: change vala_src_prepare behavior when USE=-vala
Date: Wed, 19 Sep 2012 16:33:13 -0400 [thread overview]
Message-ID: <505A2C09.6010104@gentoo.org> (raw)
In-Reply-To: <20120919203723.60c85278@googlemail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 19/09/12 03:37 PM, Ciaran McCreesh wrote:
> On Wed, 19 Sep 2012 15:26:44 -0400 Alexandre Rostovtsev
> <tetromino@gentoo.org> wrote:
>> Pacho Ramos has suggested making vala_src_prepare() into a no-op
>> in the common situation where vala is in IUSE and USE=-vala.
>
> There's no way to obtain the effective value of IUSE from within
> an ebuild or eclass. You'll need to use an independent variable to
> get this information.
>
I don't think that the 'effective' value of IUSE matters in this
particular case. This would be the 'explicit' value as is hard-coded
in the ebuild that would need to be checked against, I expect?
Unless eclasses and phase functions are in the habit of removing
entries from IUSE, I don't see this being an issue?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iF4EAREIAAYFAlBaLAkACgkQ2ugaI38ACPDeDAD9Ea1CalzAp0poqTh3mTtpwTt8
LVu5vNcZF311lIDJDE0A/jibvhrqIbB5Sw9syPvK8I0j97LGOSXPpZcfN9LYKCHF
=1wDn
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-09-19 20:35 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHG43MsUfVPXqqv-zRKH1spToR=kKQFYNfCxXjiewr=FeaV4qg@mail.gmail.com>
[not found] ` <1347928029.24984.27.camel@rook>
2012-09-19 19:26 ` [gentoo-dev] vala.eclass: change vala_src_prepare behavior when USE=-vala Alexandre Rostovtsev
2012-09-19 19:37 ` Ciaran McCreesh
2012-09-19 20:33 ` Ian Stakenvicius [this message]
2012-09-19 20:42 ` Ciaran McCreesh
2012-09-19 21:03 ` Michał Górny
2012-09-19 21:14 ` Ciaran McCreesh
2012-09-19 21:24 ` Michał Górny
2012-09-19 21:31 ` Ciaran McCreesh
2012-09-19 21:39 ` Michał Górny
2012-09-19 21:51 ` Ciaran McCreesh
2012-09-19 22:13 ` Michał Górny
2012-09-19 22:18 ` Ciaran McCreesh
2012-09-19 22:30 ` Michał Górny
2012-09-19 22:45 ` Ciaran McCreesh
2012-09-19 19:46 ` Michał Górny
2012-09-20 6:14 ` Alexandre Rostovtsev
2012-09-20 6:43 ` Pacho Ramos
2012-09-20 7:33 ` Alexandre Rostovtsev
2012-09-20 17:52 ` Pacho Ramos
2012-09-20 17:55 ` Ciaran McCreesh
2012-09-20 7:41 ` Michał Górny
2012-09-20 13:13 ` Ian Stakenvicius
2012-09-20 13:52 ` Ciaran McCreesh
2012-09-20 14:14 ` Ian Stakenvicius
2012-09-20 14:26 ` Ciaran McCreesh
2012-09-20 14:40 ` Ian Stakenvicius
2012-09-20 17:58 ` Pacho Ramos
2012-09-20 18:12 ` Michael Mol
2012-09-20 18:23 ` Ian Stakenvicius
2012-09-20 18:24 ` Ciaran McCreesh
2012-09-20 19:22 ` Ian Stakenvicius
2012-09-20 19:31 ` Ciaran McCreesh
2012-09-20 19:47 ` Ian Stakenvicius
2012-09-20 19:47 ` Ian Stakenvicius
2012-09-21 19:01 ` Pacho Ramos
2012-09-22 8:07 ` Pacho Ramos
2012-09-20 17:56 ` Pacho Ramos
2012-09-20 17:54 ` Pacho Ramos
2012-09-20 17:55 ` Ciaran McCreesh
2012-09-20 18:13 ` Pacho Ramos
2012-09-20 18:15 ` Ciaran McCreesh
2012-09-20 18:33 ` Michael Mol
2012-09-20 8:10 ` Ciaran McCreesh
2012-09-20 18:02 ` Pacho Ramos
2012-09-20 18:11 ` Ciaran McCreesh
2012-09-20 22:42 ` [gentoo-dev] " Duncan
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=505A2C09.6010104@gentoo.org \
--to=axs@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