public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] [RFC] should we do an EAPI bump now with features that are already implemented?
Date: Mon, 09 Jul 2007 15:15:36 -0700	[thread overview]
Message-ID: <4692B388.9030604@gentoo.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi everyone,

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?

Zac

[1] http://bugs.gentoo.org/show_bug.cgi?id=174380
[2] http://bugs.gentoo.org/show_bug.cgi?id=174405
[3] http://bugs.gentoo.org/show_bug.cgi?id=174410
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)

iD8DBQFGkrOF/ejvha5XGaMRArFGAKC+L57IUOy6YxjS02pn4xyv7VkvvgCg4Qxd
mE4HfMS4OotYKtW4Eql3N9s=
=OL5S
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2007-07-09 22:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 22:15 Zac Medico [this message]
2007-07-09 22:26 ` [gentoo-dev] [RFC] should we do an EAPI bump now with features that are already implemented? Ciaran McCreesh
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=4692B388.9030604@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-dev@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