On Sun, 7 Apr 2013 08:27:18 +0100
Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:

> On Sat, 6 Apr 2013 20:05:11 -0600
> Ryan Hill <dirtyepic@gentoo.org> wrote:
> > In short:
> > Toolchain packages, for better or worse, are built by eclass.  We are
> > not forward-porting toolchain.eclass every time someone decides there
> > are too many EAPIs in the tree.  Every change to that eclass breaks
> > something (the trick is to break things people don't care about any
> > more and hope no one notices).  I don't know the ins and outs of
> > glibc's eblits but I doubt they would be simple to port either.  I
> > also don't know much about toolchain-binutils.eclass, but it seems
> > like it would be doable.
> 
> Sounds like a good opportunity to replace toolchain.eclass with
> something clean and understandable.

Sure, I suppose if we were trying to break everything all at once that would
be the most efficient way to go about it.


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