| 1 |
On Sun, 17 May 2009 18:20:21 +0200 |
| 2 |
Arfrever Frehtes Taifersar Arahesis <arfrever.fta@×××××.com> wrote: |
| 3 |
> I would like to suggest to include possibility of using of features of |
| 4 |
> bash-4.0 (and older versions) in local scope of EAPI="3" ebuilds. |
| 5 |
> |
| 6 |
> I know that it's slightly late, but this change is very easy to |
| 7 |
> implement (adjusting RDEPEND of new versions of package managers and |
| 8 |
> updating PMS). |
| 9 |
|
| 10 |
No good, for two reasons. |
| 11 |
|
| 12 |
First, this is a global scope change, and we can't make global scope |
| 13 |
changes to EAPIs using current mechanisms. EAPIs have to carry on using |
| 14 |
bash 3 until the EAPI mechanism is changed. |
| 15 |
|
| 16 |
Second, by order of the Council, EAPI 3's feature list was locked |
| 17 |
several weeks ago. If we ignore that for one thing, it just means |
| 18 |
everyone else who had features that came along too late will start |
| 19 |
demanding we reconsider those too... |
| 20 |
|
| 21 |
-- |
| 22 |
Ciaran McCreesh |
Archives