You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both build.sh and gen-version use #!/bin/bash instead of #!/usr/bin/env bash which means Bash will not always be found (even on some Linux distributions!).
I'm just not sure on any disadvantages of using #!/usr/bin/env bash hence I'm not shooting in a PR right away.
edit: Konrad just replied with the reasons in chat:
That’s intentional. macOS ships a very old bash 3.2 as /bin/bash (last one that’s GPLv2) and I have a newer one in my path. I wanted to make sure that we do not use newer features.
Both
build.sh
andgen-version
use#!/bin/bash
instead of#!/usr/bin/env bash
which means Bash will not always be found (even on some Linux distributions!).The text was updated successfully, but these errors were encountered: