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.

[–] [email protected] 8 points 1 year ago (1 children)

#!/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

[–] JackbyDev 3 points 1 year ago* (last edited 1 year ago) (3 children)

Are there any distos with /usr/bin/env in a different spot? I still believe that's the best approach for getting bash.

[–] [email protected] 6 points 1 year ago (1 children)

All posix-compliant distros need /usr/bin/env

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

I do think a simple symlink is superior to a tool parsing stuff. A shame POSIX choose this approach.

Still the issue that a posix shell can be on a non-posix system and vice versa. And certificates versus used practice. Btw, isn't there only one posix certified Linux distro? Was it Suse?

[–] [email protected] 2 points 1 year ago

Posix certification is dumb but posix compliance is nice to ensure some level of compatibility.

Symlinks would be pretty bad in the case of nixos. Wouldn't fit at all

[–] [email protected] 2 points 1 year ago

My own. I use arch btw

[–] [email protected] 0 points 1 year ago (1 children)

/bin/bash won't work on every system for example NixOS some other systems may have bash in /usr/bin or elsewhere

[–] [email protected] 1 points 1 year ago (1 children)

NixOS didn't do /usr merge?

[–] [email protected] 1 points 1 year ago

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.