| 1 |
Hi, |
| 2 |
|
| 3 |
Tomáš Chvátal <scarabeus@g.o>: |
| 4 |
> > The sense of this I don't understand. You should not restrict EAPI |
| 5 |
> > like this. |
| 6 |
> > |
| 7 |
> > V-Li |
| 8 |
> > |
| 9 |
> Why not. Quite standart way. |
| 10 |
> 19 case ${EAPI:-0} in |
| 11 |
> 20 2) : ;; |
| 12 |
> 21 *) DEPEND="EAPI-TOO-OLD" ;; |
| 13 |
> 22 esac |
| 14 |
|
| 15 |
Microsoft Windows is standard software, too....you want to use it? And |
| 16 |
if an ebuild uses EAPI 3 it will fail badly, while it isn't too old. A |
| 17 |
sane assumption is that EAPI 3 will at least contain all features from |
| 18 |
EAPI 2 with very few adjustments to existing syntax and behaviour if at |
| 19 |
all. |
| 20 |
|
| 21 |
V-Li |
| 22 |
|
| 23 |
-- |
| 24 |
Christian Faulhammer, Gentoo Lisp project |
| 25 |
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
| 26 |
|
| 27 |
<URL:http://gentoo.faulhammer.org/> |
Archives