From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: ciaran.mccreesh@googlemail.com
Subject: Re: [gentoo-dev] vala.eclass: change vala_src_prepare behavior when USE=-vala
Date: Wed, 19 Sep 2012 23:24:29 +0200 [thread overview]
Message-ID: <20120919232429.222a48c6@pomiocik.lan> (raw)
In-Reply-To: <20120919221418.107b6b03@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On Wed, 19 Sep 2012 22:14:18 +0100
Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
> On Wed, 19 Sep 2012 23:03:05 +0200
> Michał Górny <mgorny@gentoo.org> wrote:
> > > No, you're not guaranteed to get the ebuild's value of IUSE, or
> > > any particular eclass's value of IUSE, or the merged value of
> > > IUSE. In particular for this case, it's possible to get false
> > > negatives.
> >
> > Then fix the spec.
>
> The spec accurately reflects the mess that is global and metadata
> variables. Portage has historically done all kinds of different things
> here (sometimes varying depending upon whether you're a binary,
> whether things are being loaded from VDB, whether env saving has
> happened previously etc), and the code is rather sensitive to
> apparently minor changes in bash versions. Thus we don't provide
> guarantees.
The historical mess is not relevant anymore. Is there a single real case
when IUSE does not contain *at least* the ebuild-set IUSE?
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2012-09-19 21:26 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
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 [this message]
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=20120919232429.222a48c6@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=ciaran.mccreesh@googlemail.com \
--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