From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] One-Day Gentoo Council Reminder for January 22
Date: Thu, 22 Jan 2009 16:11:34 +0000 [thread overview]
Message-ID: <20090122161134.7c27ed3e@snowcone> (raw)
In-Reply-To: <4977F1B5.3080608@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
On Wed, 21 Jan 2009 22:10:29 -0600
Jeremy Olexa <darkside@gentoo.org> wrote:
> I think the spec should just be upgraded because it isn't exactly
> obvious to the casual dev what is a 3.0 feature vs 3.1, etc. We
> already have 3.1 features in the tree, I'm not sure where the red
> tape is here.
The problem is, if the tree uses 3.1 and you don't have 3.1, it's a
massive pain in the ass to upgrade. We waited a loooong time between
3.0 going stable and allowing it in the tree because of that.
Ideally we'd say "no using 3.1 features unless EAPI=3", but that would
be messy with eclasses even if developers did know that += is a 3.1
feature...
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-22 16:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 23:35 [gentoo-dev] One-Day Gentoo Council Reminder for January 22 Donnie Berkholz
2009-01-22 0:02 ` Donnie Berkholz
2009-01-22 16:15 ` Ciaran McCreesh
2009-01-22 17:23 ` Tobias Scherbaum
2009-01-22 17:38 ` Donnie Berkholz
2009-01-22 19:21 ` Ulrich Mueller
2009-01-22 19:47 ` Tobias Scherbaum
2009-01-22 3:28 ` Jeremy Olexa
2009-01-22 3:38 ` Donnie Berkholz
2009-01-22 4:10 ` Jeremy Olexa
2009-01-22 16:11 ` Ciaran McCreesh [this message]
2009-01-22 16:56 ` Donnie Berkholz
2009-01-22 17:02 ` Ciaran McCreesh
2009-01-22 17:12 ` Ciaran McCreesh
2009-01-22 17:28 ` Donnie Berkholz
2009-01-22 17:37 ` 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=20090122161134.7c27ed3e@snowcone \
--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