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
On Fri, Oct 28, 2011 at 5:06 PM, Anthony G. Basile bluen...@gentoo.org wrote:
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
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
On Fri, Oct 28, 2011 at 5:17 AM, Ryan Hill dirtye...@gentoo.org wrote:
On Thu, 27 Oct 2011 23:03:12 +0530
Nirbheek Chauhan nirbh...@gentoo.org wrote:
So, I honestly see no reason why toolchain should not start using EAPI 2.
I await your patch to toolchain.eclass. :P
Sure, whenever I'm
