| 1 |
On Tuesday 11 December 2007 18:21:31 Markus Ullmann wrote: |
| 2 |
> Doug Klima schrieb: |
| 3 |
> > <Cardoe> zmedico: what if I have EAPI=2 above the inherit but an eclass |
| 4 |
> > has EAPI=1 |
| 5 |
> |
| 6 |
> if an eclass sets EAPI, then the ebuild shouldn't... make it two |
| 7 |
> eclasses if needed or plain bump them if really really needed. |
| 8 |
> |
| 9 |
> Greetz |
| 10 |
> Jokey |
| 11 |
|
| 12 |
That doesn't sound right. What happens if the eclass sets an EAPI(say 1), but |
| 13 |
you need to use say X feature(which is in EAPI 2). By what you said, this |
| 14 |
would prevent the ebuild from using the features in EAPI 2. It also isn't |
| 15 |
smart to bump eclasses' EAPI--EAPI should be set to the lowest common |
| 16 |
denominator that that feature being used is in. |
| 17 |
|
| 18 |
If that made sense ;) |
| 19 |
|
| 20 |
-- |
| 21 |
2.6.23-gentoo-r3 |
Archives