Erik de Castro Lopo wrote:
> I'm thingking og switching all the test scripts to use /bin/bash instead
> of /bin/sh.
Well, it does mean an additional bash dependency on systems that
don't natively include bash, e.g. *BSD. (And when you install bash
on these systems, it won't end up in /bin, so #
This is fine with me.
I started this process long ago as well, and would make the recommendation
that if you use BASH, keep the bashisms to BASH 2.03 or lower.
If you script wtih BASH 2 as the lowest common denominator, you'll find
that most systems are supported (even Solaris 8 -- BASH 2.03b).
On 13-09-15 3:25 PM, Erik de Castro Lopo wrote:
> I'm thingking og switching all the test scripts to use /bin/bash
Fine with me.
In theory you can do useful functions with portable shell, but it's a
testing burden, as you say.
-r
___
flac-dev mailin
On Sep 15, 2013, at 15:25, Erik de Castro Lopo wrote:
> I'm thingking og switching all the test scripts to use /bin/bash
> instead
> of /bin/sh. The main reason is that /bin/sh on linux can mean one of
> two things; bash in bourne shell comatibility mode or dash. These two
> behave differently e