| 1 |
On 11 Nov 2015 10:32, Michał Górny wrote: |
| 2 |
> I'm not convinced we ought to do this for EAPI < 6. It is a breaking |
| 3 |
> change after all, and as such changes the behavior of EAPI < 6 ebuilds. |
| 4 |
|
| 5 |
that is a false statement. anything not working with bash-3.2 is already |
| 6 |
broken according to the PMS. |
| 7 |
|
| 8 |
> There are some ebuilds/eclasses that have bash version checks, |
| 9 |
> and execute bash-4 code when bash-4 is available. As far as I |
| 10 |
> understand, this will effectively prohibit bash-4 code even though |
| 11 |
> BASH_VERSINFO will still indicate bash-4 is being used. |
| 12 |
|
| 13 |
no, that's not what it does. it changes behavior for code that itself |
| 14 |
has changed behavior between versions. it does not disable any newer |
| 15 |
functionality. it would have been nice to have a knob that would turn |
| 16 |
off newer functionality as well, but upstream didn't seem keen on it. |
| 17 |
-mike |
Archives