From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: 'mad' vs 'mp3' USE flags
Date: Sat, 15 Jul 2006 11:26:13 -0400 [thread overview]
Message-ID: <44B90915.2040806@gentoo.org> (raw)
In-Reply-To: <e9agfu$puj$1@sea.gmane.org>
Duncan wrote:
> Zac Medico <zmedico@gentoo.org> posted 44B7FD7A.6010209@gentoo.org,
> excerpted below, on Fri, 14 Jul 2006 13:24:26 -0700:
>
>>> Per-package use.mask is not here for another year and in the mean time I
>>> needed a working solution, this is it.
>> It think we can have it sooner than "another year". There are lots of
>> fixes in 2.1.1_pre and I'd like to close the merge window pretty soon so
>> that it can be stabilized. I'll work on a patch for package.use and
>> package.use.mask so that we should be able to have it in a stable 2.1.1
>> release within a month or two.
>
> PMFJI but don't we have to keep compatibility with old versions for a year
> (well, from my read, I believe the precedent is 10 months) after the change
> hits stable, or did the discussion I remember reading a bit of decide say
> 6 months was enough?
>
> Even if EAPI is used, previous policy would have put it nearly a year from
> now, as EAPI was only introduced with 2.1.0, or was it backported?
>
> I've seen discussion of both points above, but no definitive policy
> changes. If I've missed the decisions, others may have as well, so
> maybe others will find the answers helpful too.
EAPI support was in for the 2.0.X version of portage, released on Dec.
1st 2005. Generally we wait 6 months (one release cycle) for new features.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-15 15:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 4:03 [gentoo-dev] 'mad' vs 'mp3' USE flags Daniel Watkins
2006-07-14 14:20 ` Diego 'Flameeyes' Pettenò
2006-07-14 14:43 ` Chris Gianelloni
2006-07-14 14:59 ` Ciaran McCreesh
2006-07-14 17:49 ` [gentoo-dev] " Daniel Watkins
2006-07-14 17:59 ` Ciaran McCreesh
2006-07-14 18:14 ` [gentoo-dev] " Chris Gianelloni
2006-07-14 18:34 ` Ciaran McCreesh
2006-07-14 15:09 ` Diego 'Flameeyes' Pettenò
2006-07-14 18:20 ` Chris Gianelloni
2006-07-14 18:42 ` Diego 'Flameeyes' Pettenò
2006-07-14 18:45 ` Chris Gianelloni
2006-07-16 4:38 ` Mike Frysinger
2006-07-14 18:24 ` Simon Stelling
2006-07-14 18:43 ` Diego 'Flameeyes' Pettenò
2006-07-14 20:24 ` Zac Medico
2006-07-14 20:31 ` Diego 'Flameeyes' Pettenò
2006-07-15 10:36 ` [gentoo-dev] " Duncan
2006-07-15 15:26 ` Alec Warner [this message]
2006-07-14 14:38 ` [gentoo-dev] " Chris Gianelloni
2006-07-14 14:51 ` Diego 'Flameeyes' Pettenò
2006-07-14 16:32 ` Jason Wever
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=44B90915.2040806@gentoo.org \
--to=antarus@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