Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-project
Lists: gentoo-project: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-project@g.o
From: Ryan Hill <dirtyepic@g.o>
Subject: Re: On eclass APIs
Date: Wed, 28 Dec 2011 23:27:51 -0600
On Tue, 27 Dec 2011 20:35:36 +0100
Fabian Groffen <grobian@g.o> wrote:

> Is this necessary for just one function, or is this only beneficial
> after a huge revamp of some eclass?  Is it acceptable to take the
> breakage outside Gentoo, given the extra work imposed by creating
> revisions and keeping track?

If there has been some major instance of eclass API breakage wrecking the tree
lately then I missed it (lately being defined as "since 2007 when
debug.eclass was purposely poisoned by QA"). So this versioning scheme is IMO
largely over-engineering a solution to a non-existent problem.

I'd like to say "use common sense" when announcing modifications to public
APIs, but we've proven time and again incapable of doing anything without a
painstakingly written procedure that we can all ignore or find loopholes in.
So 30 days sounds like a good minimum for an email to g-d-announce after all
in-tree uses are converted, unless your eclass has an "s", "y", or "e" in the
name in which case you roll a die and multiply by 30 (ie. current standard

fonts, gcc-porting,                  it makes no sense how it makes no sense
toolchain, wxwidgets                           but i'll take it free anytime
@                EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
signature.asc (PGP signature)
On eclass APIs
-- Fabian Groffen
Lists: gentoo-project: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: On eclass APIs
Next by thread:
Re: On eclass APIs
Previous by date:
Re: On eclass APIs
Next by date:
Re: On eclass APIs

Updated Jul 05, 2012

Summary: Archive of the gentoo-project mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.