On 8/14/24 2:25 AM, Martin Kealey wrote:
Hi Chet
I have worked up a patch that considerably simplifies the logic for
setting and displaying the shopt compatXX settings, by getting rid of
the numberous boolean variables and simply computing the setting level
directly.
Thanks. The boolean variab
Hi Chet
I have worked up a patch that considerably simplifies the logic for
setting and displaying the shopt compatXX settings, by getting rid of
the numberous boolean variables and simply computing the setting level
directly.
However before I submit my compatXX patch, I would like to ensure I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/20/15 2:49 PM, Mike Frysinger wrote:
I mean, in theory, it's simple to do that:
unset BASH_COMPAT
shopt -u compat31
command shopt -s compat32 2>/dev/null
>>>
>>> ... but that doesn't work in bash-3.2:
>>> $ bash-3.2 -c '
On 16 Oct 2015 11:37, Chet Ramey wrote:
> On 10/15/15 5:30 PM, Mike Frysinger wrote:
> >>> the bash compat feature seems to address this nicely: our standard says
> >>> we should use bash-3.2, so we set the compat level to that, and then we
> >>> have much stronger confidence in newer versions not
On 16 Oct 2015 14:26, Chet Ramey wrote:
> On 10/16/15 11:37 AM, Chet Ramey wrote:
> > unset BASH_COMPAT
> > shopt -u compat31 compat32 compat40 compat41
> > shopt -s compat42 2>/dev/null || :
> >
> > to set shell_compatibility_level to 42 on bash versions >= bash-4.2.
> >
> > (this needs the atta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/16/15 11:37 AM, Chet Ramey wrote:
> unset BASH_COMPAT
> shopt -u compat31 compat32 compat40 compat41
> shopt -s compat42 2>/dev/null || :
>
> to set shell_compatibility_level to 42 on bash versions >= bash-4.2.
>
> (this needs the attached pat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/15 5:30 PM, Mike Frysinger wrote:
> that assumes that behavior changes only once between versions. pretty su
re
> we've seen changes where bash-3.2 did one thing, bash-4.3 did something e
lse,
> and versions in between did yet another thing.
On 15 Oct 2015 16:06, Chet Ramey wrote:
> On 10/15/15 3:27 PM, Mike Frysinger wrote:
> > our build environment relies heavily on bash. in our ebuild standard, we
> > declare the min version of bash that is supported (3.2 currently). this
> > way we don't have people using features found only in n
Mike Frysinger wrote:
our build environment relies heavily on bash. in our ebuild standard, we
declare the min version of bash that is supported (3.2 currently). this
way we don't have people using features found only in newer versions and
breaking on systems with older versions of bash.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/15 3:27 PM, Mike Frysinger wrote:
> On 15 Oct 2015 14:28, Chet Ramey wrote:
>> On 10/15/15 1:34 PM, Mike Frysinger wrote:
>>> with bash-4.0, new compat options were introduced:
>>> shopt -s compat32
You've picked the story up in the middl
On 15 Oct 2015 14:28, Chet Ramey wrote:
> On 10/15/15 1:34 PM, Mike Frysinger wrote:
> > with bash-4.0, new compat options were introduced:
> > shopt -s compat32
> > and with bash-4.3, a variable was added:
> > export BASH_COMPAT=3.2
> >
> > but things get a little weird when you want to s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/15 1:34 PM, Mike Frysinger wrote:
> with bash-4.0, new compat options were introduced:
> shopt -s compat32
> and with bash-4.3, a variable was added:
> export BASH_COMPAT=3.2
>
> but things get a little weird when you want to set
Mike Frysinger wrote:
with bash-4.0, new compat options were introduced:
shopt -s compat32
and with bash-4.3, a variable was added:
export BASH_COMPAT=3.2
shopt -p|grep compat43
# (no output)
---
Maybe if you could check if there is a compat setti
with bash-4.0, new compat options were introduced:
shopt -s compat32
and with bash-4.3, a variable was added:
export BASH_COMPAT=3.2
but things get a little weird when you want to set the compat level to
the current version:
$ echo $BASH_VERSION
4.3.42(1)-release
14 matches
Mail list logo
