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