1 |
On Tuesday 16 December 2008 18:46:44 Jeremy Olexa wrote: |
2 |
> Exhibit A: |
3 |
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/python.eclass?r1=1.4 |
4 |
> 8&r2=1.49 |
5 |
> |
6 |
> This causes me pain on my hosts that don't have >=bash-3.1[0] for |
7 |
> /bin/bash. Because I can't install portage with an old bash until I |
8 |
> get a new python installed which uses python.eclass which isn't |
9 |
> supported with my /bin/bash (quite circular indeed) |
10 |
> |
11 |
> Technically there are workarounds for me...but it is still annoying. |
12 |
> So...what do we do? A) Specifically allow >=bash-3.1 features in |
13 |
> ebuilds/eclasses. or B) revert the commit because the PMS says[1] that |
14 |
> we comply with >bash-3.0 |
15 |
> |
16 |
> Please discuss, thanks. |
17 |
|
18 |
btw, latest python.eclass requires bash-3.2+ due to parsing errors in the |
19 |
regex checks: |
20 |
$ bash-3.1 -c '[[ a =~ ^(a|b)$ ]]' |
21 |
bash-3.1: -c: line 0: syntax error in conditional expression: unexpected token `(' |
22 |
bash-3.1: -c: line 0: syntax error near `^(a' |
23 |
|
24 |
we could quote these or require bash-3.2+ ... |
25 |
-mike |