1 |
On 22 Oct 2015 17:00, Ulrich Mueller wrote: |
2 |
> >>>>> On Thu, 22 Oct 2015, Mike Frysinger wrote: |
3 |
> > On 21 Oct 2015 09:34, Ulrich Mueller wrote: |
4 |
> >> "The interpreter is assumed to be GNU bash, version as listed in |
5 |
> >> table xyz, or any later version. If possible, the package manager |
6 |
> >> should set the shell's compatibility level to the exact version |
7 |
> >> specified. It must ensure that any such compatibility settings |
8 |
> >> (e.g. the BASH_COMPAT variable) are not exported to external |
9 |
> >> programs." |
10 |
> |
11 |
> > why not include the shell script snippet too ? |
12 |
> |
13 |
> I'd rather not. BASH_COMPAT doesn't work with <bash-4.3 (one has to |
14 |
> use compatXX there) and also we don't know if the method won't change |
15 |
> again in future versions of bash. |
16 |
|
17 |
Chet seemed pretty intent on BASH_COMPAT sticking around and being |
18 |
the future while the compat options are being killed off |
19 |
|
20 |
imo, we should have more code snippets in PMS like this to assist people |
21 |
implementing PMs. it would be noise though for people who just want the |
22 |
spec reference (with a focus on ebuilds), so maybe we need a knob to output |
23 |
these things ? i've read specs where various snippets/asides/remarks are |
24 |
inlined and it really helps to clarify thinking/intentions. |
25 |
-mike |