[gentoo-project] Re: Call for agenda items - Council meeting 2013-04-09

[Ryan Hill <dirtyepic@gentoo.org>]

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

On Wed, 10 Apr 2013 16:22:29 -0400
Rich Freeman <rich0@gentoo.org> wrote:

> On Wed, Apr 10, 2013 at 3:30 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> > we can could create a "toolchain-stable.eclass".  whenever we stabilize a
> > new version, we copy the current toolchain.eclass to
> > toolchain-stable.eclass and change the newly stabilized ebuild to inherit
> > that instead.

That might worth a shot.

> toolchain.eclass is only used by gcc, kgcc64, and gcc-apple.  Would it
> just make more sense to inline it?  That makes all these issues go
> away - each version has its own independent quality process and there
> is no risk of changes breaking things across versions.

While that's true, we often do make changes that need to be applied to all
versions.  The more each ebuild diverges from each other, the greater the
likelihood of conflicts that will have to be individually inspected.

I used to inline parts of toolchain_src_unpack in the live vcs ebuilds and
I constantly had to sync them to the eclass by hand.  And that's just 3
ebuilds.  There are over 200 of them in the toolchain overlay.


-- 
gcc-porting
toolchain, wxwidgets                                     by design, by neglect
@ gentoo.org                                     for a fact or just for effect

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