[PATCH 1 of 2 V2] contrib: don't hardcode path to bash interpreter

[David Soria Parra]

Julien Cristau <julien.cristau at logilab.fr> writes:

> On Wed, Mar 26, 2014 at 12:02:44 +0100, Olle Lundberg wrote:
>
>> # HG changeset patch
>> # User Olle Lundberg <geek at nerd.sh>
>> # Date 1395831553 -3600
>> #      Wed Mar 26 11:59:13 2014 +0100
>> # Node ID 6e8b538637302e06a3510d15e36c30757f8501a2
>> # Parent  2a14a2e1ec78f2950da46fedb70686278d90620e
>> contrib: don't hardcode path to bash interpreter
>> 
>> Use the env binary to figure out the correct bash to use.
>> Certain systems ships with an ancient version of bash, but the
>> user might have installed a newer one that is earlier in $PATH.
>> 
>> For example the current version of Mac OS X ships version 3.2.51
>> of bash, which does not understand new fancy builtins such as
>> readarray. A user might install a newer version of bash, use that
>> as their shell and add that path before bin.
>> 
> Why does that mean these scripts shouldn't use the bash version in /bin?
> Do they need any fancy new bash features?

Operating systems like Solaris 10 don't necessrily have a /bin/bash.