On 10/27/2011 07:50 PM, Mike Frysinger wrote:
> On Fri, Oct 28, 2011 at 01:47, Ryan Hill wrote:
>> On Thu, 27 Oct 2011 23:03:12 +0530 Nirbheek Chauhan wrote:
>>> So, I honestly see no reason why toolchain should not start using EAPI 2.
>> I await your patch to toolchain.eclass. :P
> i wouldn't bother as it's most likely not going to be accepted at this time
>
> (i haven't kept up-to-date with the hardened threads as i'm traveling atm)
> -mike
>
I wouldn't even worry about the hardened stuff right now, just getting
toolchain.eclass EAPI>=2 would be a step forward.
Approaching this naively, can't we just set EAPI="2" in the eclass, see
what breaks and fix? Or is it more involved because some EAPI="0"
ebuilds would be inheriting it and we'd need a lot of if "${EAPI}" == 0
checks interspersed through the eclass?
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : [email protected]
GnuPG FP : 8040 5A4D 8709 21B1 1A88 33CE 979C AF40 D045 5535
GnuPG ID : D0455535
