From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] should we do an EAPI bump now with features that are already implemented?
Date: Mon, 9 Jul 2007 23:26:19 +0100 [thread overview]
Message-ID: <20070709232619.7d7052b5@snowflake> (raw)
In-Reply-To: <4692B388.9030604@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Mon, 09 Jul 2007 15:15:36 -0700
Zac Medico <zmedico@gentoo.org> wrote:
> Bug 174380 [1] has a growing list of features that may be included in
> EAPI-1. Some of the features are already implemented but can't be
> used in the portage tree until we do an EAPI bump. The ones that are
> currently implemented include slot deps [2] and iuse defaults [3].
> Are these features important enough to warrant an EAPI bump or should
> we wait for more features to materialize?
No point waiting when there're useful things that can be done straight
away. Slot deps at least meet that.
As for IUSE defaults... There were objections against that feature on
the grounds that it's unnecessary and increased maintenance. Do they
really offer any benefit over package.use?
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-09 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 22:15 [gentoo-dev] [RFC] should we do an EAPI bump now with features that are already implemented? Zac Medico
2007-07-09 22:26 ` Ciaran McCreesh [this message]
2007-07-10 5:17 ` Mike Frysinger
2007-07-09 22:28 ` Petteri Räty
2007-07-10 16:01 ` Zac Medico
2007-07-10 16:50 ` Petteri Räty
2007-07-10 17:14 ` Ciaran McCreesh
2007-07-10 17:26 ` Petteri Räty
2007-07-10 17:32 ` Ciaran McCreesh
2007-07-10 17:37 ` Petteri Räty
2007-07-10 6:14 ` [gentoo-dev] " Stefan Schweizer
2007-07-10 8:08 ` Marius Mauch
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=20070709232619.7d7052b5@snowflake \
--to=ciaranm@ciaranm.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