1 |
On Mon, Dec 19, 2005 at 05:24:06PM +0000, Ciaran McCreesh wrote: |
2 |
> On Mon, 19 Dec 2005 17:49:02 +0100 Marius Mauch <genone@g.o> |
3 |
> wrote: |
4 |
> | And just in case anybody wonders: this cannot be fixed with EAPI or |
5 |
> | adding a portage dep on packages as those only take effect when the |
6 |
> | ebuild is already parsed while the mentioned problems occur much |
7 |
> | earlier. |
8 |
> |
9 |
> Is it too late to switch to .ebuild.2, .ebuild.3 etc instead of making |
10 |
> EAPI an internal variable? |
11 |
Yes. |
12 |
|
13 |
EAPI mechanism will work as long as the ebuild is still valid shell |
14 |
(eclasses complicate this, but the upcoming eclass2 switch over is the |
15 |
only issue). EAPI isn't going to be 5 versions in 5 years, I'd expect |
16 |
2-3 version a year. |
17 |
|
18 |
Any time we extend the api of provided functions to the ebuild env, we |
19 |
should be bumping EAPI so the ebuild is known to work. |
20 |
~harring |