1 |
On Fri, Oct 28, 2011 at 5:06 PM, Anthony G. Basile <blueness@g.o> wrote: |
2 |
> Approaching this naively, can't we just set EAPI="2" in the eclass, see |
3 |
> what breaks and fix? Or is it more involved because some EAPI="0" |
4 |
> ebuilds would be inheriting it and we'd need a lot of if "${EAPI}" == 0 |
5 |
> checks interspersed through the eclass? |
6 |
> |
7 |
|
8 |
afaik, eclasses aren't supposed to be setting EAPI. They can choose to |
9 |
not support some EAPIs and error out, but they need checks. |
10 |
|
11 |
Mostly, eclasses read ${EAPI} to do conditional exporting of phases |
12 |
and conditional usage of features. |
13 |
|
14 |
|
15 |
-- |
16 |
~Nirbheek Chauhan |
17 |
|
18 |
Gentoo GNOME+Mozilla Team |