| 1 |
On Tue, 10 Jun 2008 22:16:21 -0700 |
| 2 |
Brian Harring <ferringb@×××××.com> wrote: |
| 3 |
> > Also, there is absolutely no reason for all future EAPIs to be a |
| 4 |
> > superset of old eapis. |
| 5 |
> |
| 6 |
> .ebuild-$EAPI-n requires all *versioning rules* to be a superset of |
| 7 |
> $EAPI=(n-1); if in doubt, re-read my example above. |
| 8 |
|
| 9 |
No it doesn't. It requires that versions be mappable to a single, |
| 10 |
enumerable master version format. Big difference. You could quite |
| 11 |
happily add -scm and remove _p in future EAPIs, for example. |
| 12 |
|
| 13 |
-- |
| 14 |
Ciaran McCreesh |
Archives