| 1 |
Matti Bickel posted on Sun, 19 Sep 2010 21:14:56 +0200 as excerpted: |
| 2 |
|
| 3 |
> It is made a requirement that per-package eclasses can not modify the |
| 4 |
> ``EAPI`` variable. It is assumed ``EAPI``, if it set, is set before |
| 5 |
> calling pkg-inherit. |
| 6 |
> |
| 7 |
> Backwards Compatibility |
| 8 |
> ======================= |
| 9 |
> |
| 10 |
> The current Package Manager Specification requires package managers to |
| 11 |
> ignore anything in the top-level package directory that does not have a |
| 12 |
> filename ending in ".ebuild" ([1]_). Thus package manager which do not |
| 13 |
> implement the per-package eclass feature can ignore them. They, however, |
| 14 |
> will fail to execute ebuilds making use of the new ``pkg-inherit`` |
| 15 |
> function. It is therefore required this feature be made part of a new |
| 16 |
> EAPI. |
| 17 |
|
| 18 |
AFAIK these two paragraphs together contradict each other in regard to |
| 19 |
eapi. |
| 20 |
|
| 21 |
Given that no set eapi is taken to be eapi=0, and this is proposed as part |
| 22 |
of a new eapi, eapi MUST be set before pkg-inherit, if pkg-inherit and |
| 23 |
thus per-pkg eclasses are to be used at all. The last sentence of the top |
| 24 |
paragraph (of the two) should therefore be rewritten to reflect that |
| 25 |
requirement and avoid any confusion. |
| 26 |
|
| 27 |
-- |
| 28 |
Duncan - List replies preferred. No HTML msgs. |
| 29 |
"Every nonfree program has a lord, a master -- |
| 30 |
and if you use the program, he is your master." Richard Stallman |
Archives