From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Add "test" to IUSE_IMPLICIT
Date: Sun, 3 Feb 2013 02:07:20 -0600 [thread overview]
Message-ID: <20130203020720.59cc0f0a@caribou> (raw)
In-Reply-To: 20130202233325.GA4159@gengoff.local.grandmasfridge.org
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
On Sat, 2 Feb 2013 23:33:26 +0000
"Aaron W. Swenson" <titanofold@gentoo.org> wrote:
> After years of "if use test ; then ..." just working when
> FEATURES="test" is declared, it isn't working with EAPI5.
I would say that's a bug fix. If you're checking if a USE flag is set then it
had better be in IUSE.
--
gcc-porting
toolchain, wxwidgets learn a language baby, it's that kind of place
@ gentoo.org where low card is hunger and high card is taste
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-02-03 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 23:33 [gentoo-dev] Add "test" to IUSE_IMPLICIT Aaron W. Swenson
2013-02-02 23:50 ` Michał Górny
2013-02-02 23:52 ` Ciaran McCreesh
2013-02-03 1:37 ` Aaron W. Swenson
2013-02-03 1:42 ` Ian Stakenvicius
2013-02-03 8:07 ` Ryan Hill [this message]
2013-02-03 8:20 ` Ralph Sennhauser
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=20130203020720.59cc0f0a@caribou \
--to=dirtyepic@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