[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev] Re: [PATCH] Recommend setting the bash compatibility level. (was: Re: utilizing BASH_CO
From:       Mike Frysinger <vapier () gentoo ! org>
Date:       2015-10-22 15:21:28
Message-ID: 20151022152128.GL26317 () vapier ! lan
[Download RAW message or body]


On 22 Oct 2015 17:00, Ulrich Mueller wrote:
> >>>>> On Thu, 22 Oct 2015, Mike Frysinger wrote:
> > On 21 Oct 2015 09:34, Ulrich Mueller wrote:
> >> "The interpreter is assumed to be GNU bash, version as listed in
> >> table xyz, or any later version. If possible, the package manager
> >> should set the shell's compatibility level to the exact version
> >> specified. It must ensure that any such compatibility settings
> >> (e.g. the BASH_COMPAT variable) are not exported to external
> >> programs."
> 
> > why not include the shell script snippet too ?
> 
> I'd rather not. BASH_COMPAT doesn't work with <bash-4.3 (one has to
> use compatXX there) and also we don't know if the method won't change
> again in future versions of bash.

Chet seemed pretty intent on BASH_COMPAT sticking around and being
the future while the compat options are being killed off

imo, we should have more code snippets in PMS like this to assist people
implementing PMs.  it would be noise though for people who just want the
spec reference (with a focus on ebuilds), so maybe we need a knob to output
these things ?  i've read specs where various snippets/asides/remarks are
inlined and it really helps to clarify thinking/intentions.
-mike

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]