| 1 |
>>>>> On Wed, 11 Nov 2015, Michał Górny wrote: |
| 2 |
|
| 3 |
> I'm not convinced we ought to do this for EAPI < 6. It is a breaking |
| 4 |
> change after all, and as such changes the behavior of EAPI < 6 |
| 5 |
> ebuilds. |
| 6 |
|
| 7 |
Which according to PMS should assume bash version 3.2. Also, AFAICS |
| 8 |
the only feature where the compat settings could have any impact is |
| 9 |
this setting from compat42: |
| 10 |
|
| 11 |
If set, bash does not process the replacement string in the pattern |
| 12 |
substitution word expansion using quote removal. |
| 13 |
|
| 14 |
All other compat changes affect either only POSIX mode, or interactive |
| 15 |
mode, or string comparison (where the compat32 setting disables locale |
| 16 |
specific behaviour and uses strcmp instead, so effectively the compat |
| 17 |
setting should be saner). |
| 18 |
|
| 19 |
> There are some ebuilds/eclasses that have bash version checks, |
| 20 |
> and execute bash-4 code when bash-4 is available. As far as I |
| 21 |
> understand, this will effectively prohibit bash-4 code even though |
| 22 |
> BASH_VERSINFO will still indicate bash-4 is being used. |
| 23 |
|
| 24 |
The compat settings don't disable any new features. They only restore |
| 25 |
previous behaviour where there was an incompatible change. |
| 26 |
|
| 27 |
Ulrich |
Archives