On Fri, Oct 28, 2011 at 5:06 PM, Anthony G. Basile <[email protected]> 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 interspersed through the eclass?
>
afaik, eclasses aren't supposed to be setting EAPI. They can choose to
not support some EAPIs and error out, but they need checks.
Mostly, eclasses read ${EAPI} to do conditional exporting of phases
and conditional usage of features.
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team
