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