Still don't do this. If you use bash specific syntax with this head, that's a bashism and causes issues with people using zsh for example. Or with Debian/*buntu, who use dash as init shell.
Just use #!/bin/bash or #!/usr/bin/env bash if you're funny.
#!/bin/bash doesn't work on NixOS since bash is in the nix store somewhere, #!/usr/bin/env bash resolves the correct location regardless of where bash is
Are there any distos with /usr/bin/env in a different spot? I still believe that's the best approach for getting bash.
/bin/bash won't work on every system
for example NixOS
some other systems may have bash in /usr/bin or elsewhere
NixOS didn't do /usr merge?
Binaries are not in /usr/bin or /bin except for /bin/sh and /usr/bin/env. Programs should not assume fixed paths for binaries and instead look for them in $PATH.
Still don't do this. If you use bash specific syntax with this head, that's a bashism and causes issues with people using zsh for example. Or with Debian/*buntu, who use dash as init shell.
Just use
#!/bin/bashor#!/usr/bin/env bashif you're funny.#!/bin/bashdoesn't work on NixOS since bash is in the nix store somewhere,#!/usr/bin/env bashresolves the correct location regardless of where bash isAre there any distos with
/usr/bin/envin a different spot? I still believe that's the best approach for getting bash.My own. I use arch btw
/bin/bashwon't work on every system for example NixOS some other systems may have bash in /usr/bin or elsewhereNixOS didn't do /usr merge?
Binaries are not in
/usr/binor/binexcept for/bin/shand/usr/bin/env. Programs should not assume fixed paths for binaries and instead look for them in$PATH.