| 1 |
On Wed, 12 Dec 2007 23:14:24 +0100 |
| 2 |
Carsten Lohrke <carlo@g.o> wrote: |
| 3 |
> I disagree here. It would be annoying and possibly even hindering in |
| 4 |
> future not being able to use higher EAPI features in eclasses. Point |
| 5 |
> is the eclass has to check, if the author of an ebuild sets another |
| 6 |
> EAPI and throw an error, in this case. |
| 7 |
|
| 8 |
There is no way for an eclass to throw an error. Nor, with the current |
| 9 |
way Portage implements EAPI, is there a way to add such a way. |
| 10 |
|
| 11 |
> The most basic issue, which we didn't even discuss yet, afaik, is how |
| 12 |
> to make every developer aware which feature belongs to which EAPI. I |
| 13 |
> freely admit, I do not know that. Is there a list somewhere? |
| 14 |
|
| 15 |
It's in PMS. svn co http://svn.repogirl.net/pms for a copy. |
| 16 |
|
| 17 |
-- |
| 18 |
Ciaran McCreesh |
Archives