From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Preparing profiles for EAPI 3 IUSE strictness
Date: Fri, 10 Jul 2009 11:05:14 +0100 [thread overview]
Message-ID: <20090710110514.37f6b6ed@snowmobile> (raw)
In-Reply-To: <200907080502.39186.Arfrever@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Wed, 8 Jul 2009 05:02:34 +0200
Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org> wrote:
> > IUSE_IMPLICIT="build debug"
> >
> > Are people wanting to make those implicit?
>
> IMHO they shouldn't be implicit.
I should probably explain the rationale behind those two...
Back in the day, various eclasses would do 'if use build' and 'if use
debug' and the like, and at one point eutils had a DEPEND="!build?
( patch )" in there.
I *think* all the major offenders there are gone now. On the other
hand, if they're not, and IUSE_IMPLICIT doesn't include those, it means
EAPI 3 won't be usable with certain fairly common eclasses.
Historically, IUSE was purely a visual thing, and didn't affect package
manager behaviour. With the introduction of the newuse stuff, and
later, use dependencies, that slowly stopped being true, and IUSE
started to matter a lot more.
> (And maybe IUSE_IMPLICIT shouldn't be supported at all.)
Personally I hate the whole implicit thing, and would rather everyone
stuck absolutely everything in IUSE. But a majority of developers
thought otherwise.
There were also calls for some fancy prefix use flags to go in
IUSE_IMPLICIT at some point. Alas, it doesn't look like something we
could have excluded from the specification entirely...
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-07-10 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 23:01 [gentoo-dev] Preparing profiles for EAPI 3 IUSE strictness Ciaran McCreesh
2009-07-07 6:08 ` Andrew D Kirch
2009-07-07 6:27 ` Brian Harring
2009-07-07 13:24 ` Andrew D Kirch
2009-07-07 8:46 ` Alec Warner
2009-07-07 13:52 ` Ciaran McCreesh
2009-07-07 14:04 ` Nirbheek Chauhan
2009-07-11 3:54 ` Andrew D Kirch
2009-07-08 3:02 ` Arfrever Frehtes Taifersar Arahesis
2009-07-10 10:05 ` Ciaran McCreesh [this message]
2009-07-10 17:32 ` Harald van Dijk
2009-07-10 17:38 ` Ciaran McCreesh
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=20090710110514.37f6b6ed@snowmobile \
--to=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