| 1 |
Ciaran McCreesh wrote: |
| 2 |
> On Wed, 12 Dec 2007 23:14:24 +0100 |
| 3 |
> Carsten Lohrke <carlo@g.o> wrote: |
| 4 |
>> I disagree here. It would be annoying and possibly even hindering in |
| 5 |
>> future not being able to use higher EAPI features in eclasses. Point |
| 6 |
>> is the eclass has to check, if the author of an ebuild sets another |
| 7 |
>> EAPI and throw an error, in this case. |
| 8 |
> |
| 9 |
> There is no way for an eclass to throw an error. Nor, with the current |
| 10 |
> way Portage implements EAPI, is there a way to add such a way. |
| 11 |
|
| 12 |
How bout declaring all supported (possibly with later conditional checks |
| 13 |
on EAPI variable etc) EAPIs in eclass via some variable, and repoman |
| 14 |
checking that EAPI set in the ebuild is compatible with all inherited |
| 15 |
eclasses? And if you need newer EAPI in the ebuild, get eclasses updated |
| 16 |
first (even if its just updating the compatibility declaration). |
| 17 |
Also, repoman could check that EAPI is not being set in the eclass. |
| 18 |
|
| 19 |
VB |
| 20 |
-- |
| 21 |
gentoo-dev@g.o mailing list |
Archives