1 |
On Tue, 11 Dec 2007 16:59:28 -0500 |
2 |
Doug Klima <cardoe@g.o> wrote: |
3 |
> discuss. |
4 |
|
5 |
* EAPI may only be set before the 'inherit' in an ebuild. |
6 |
|
7 |
* Eclasses may not set EAPI. |
8 |
|
9 |
* Eclasses may not assume a particular EAPI. |
10 |
|
11 |
* If an eclass needs to work with multiple EAPIs, EAPI-specific code |
12 |
should be split out into foo-eapiBLAH.eclass, and EAPI-agnostic code |
13 |
and a conditional inherit should remain in foo.eclass. |
14 |
|
15 |
* Eclasses cannot be made not to work with any given EAPI. If such |
16 |
functionality is desirable, someone needs to file an EAPI request for |
17 |
permitting an alternative to 'die' that is legal in global scope. |
18 |
|
19 |
-- |
20 |
Ciaran McCreesh |