Yes

Mac@programming.dev to Programmer Humor@programming.dev – 774 points –
81

You are viewing a single comment

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.

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

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?

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

1 more...
1 more...

/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.

1 more...