public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Last rites: ccc.eclass
Date: Tue, 26 Jan 2010 01:17:27 -0600	[thread overview]
Message-ID: <20100126011727.4279a125@gentoo.org> (raw)
In-Reply-To: 4B51BF4C.7070807@gentoo.org

[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]

On Sat, 16 Jan 2010 15:29:48 +0200
Petteri Räty <betelgeuse@gentoo.org> wrote:

> On 01/12/2010 12:23 AM, Brian Harring wrote:
> > On Mon, Jan 11, 2010 at 09:25:51PM +0100, Raaal Porcel wrote:
> >> scarabeus told me that the eclass can't be removed until two years since
> >> the deprecation date, so...
> >>
> >> Removal of the eclass on 2012/01/11
> > 
> > Reasoning?  Prior to env saving we couldn't particularly punt 
> > eclasses, but env saving is widely deployed now...
> > 
> > ~harring
> 
> At least my argument at the time was that better to be safe when the
> benefit from removing old eclasses isn't that much.

Still, waiting another two years to be able to remove an eclass which
itself hasn't been used in two years seems a little ridiculous.  I can see
waiting two years from when env saving went into stable, but that's passed
already.

wxlib.eclass was recently removed (accidentally) after being
deprecated for just a couple months, and the world continued to revolve
despite it. ;)


-- 
fonts,                                looks like Christmas at 55 degrees
gcc-porting,                              this latitude weakens my knees
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-01-26  7:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 18:02 [gentoo-dev] Last rites: ccc.eclass Raúl Porcel
2010-01-11 20:25 ` Raúl Porcel
2010-01-11 22:23   ` Brian Harring
2010-01-11 23:15     ` Tomáš Chvátal
2010-01-16 13:29     ` Petteri Räty
2010-01-26  7:17       ` Ryan Hill [this message]

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=20100126011727.4279a125@gentoo.org \
    --to=dirtyepic@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