1 |
This has been on my list for a while, Brian Harring put EAPI into |
2 |
portage 2.0.53; it's used for introducting new features into the tree. |
3 |
|
4 |
A) Are we planning on using it at all? I like the idea of it, but no |
5 |
one has really said much about it besides Brian himself. If so I'll |
6 |
work up a list of things affected ( there is one in bzr somewhere ) |
7 |
|
8 |
>From my POV there is nothing wrong with bumping the EAPI of portage now, |
9 |
the only time it ever affects users is when ebuilds set it and IIRC, |
10 |
nothing in the tree uses it yet. However there are features that people |
11 |
want backported ( phase hooks, || () handing, etc.. ) that we need to |
12 |
control. For now people are just DEPENDing on the version of portage |
13 |
that supports their behavior. |
14 |
|
15 |
Basically, is anyone against EAPI, and why; otherwise I will start |
16 |
writing the documentation for it (manpages) and add things for the |
17 |
devrel guide and probably the unofficial developer handbook. |
18 |
|
19 |
Also the concensus on releasing EAPI to the public was originally 6 |
20 |
months from it's inception, EAPI=0 went stable in 2.0.53, released |
21 |
December 1st. Does anyone see a need to release it at a different date? |
22 |
|
23 |
-Antarus |