[BUG] The script may still be ran under old bash on macOS

[jgabaut]

At the moment the script's shebangs points to /bin/bash. While this is fine and dandy on most systems, on macOS (which still ships bash 3.2) this may lead to unknown errors.

This is mostly because the newer bash you can get from homebrew will reside somewhere like /opt/homebrew/bin/bash.

I don't think running chsh and updating the shells info does anything to change which program will correspond to /bin/bash...

Needs further investigation.

To show the unexpected behaviour on macOS:

• Run brew install bash and install the recent one
• Ensure you follow the needed steps to update your system shells
• Run amboso
• A warning for bash version <4 can be seen, something like

  [WARN]    Bash version: {3.2.57(1)-release} is less than 4

• Try the same test that triggers the warning, but in an interactive shell:

  $ echo $BASH_VERSINFO
  > 5

• This happens because even though your interactive shell is updated, the one called to interpret the amboso script is still /bin/bash.

[jgabaut]

Version 2.0.5 changes the shebangs to point to /usr/bin/env bash, allowing an updated bash to be picked up when on macOS. This should have been done ages ago, about #58 .

[jgabaut]

This should have been closed earlier, since its main goal has been achieved.