784
Yes
(programming.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Nov 2023
784 points (100.0% liked)
Programmer Humor
19544 readers
420 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
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.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
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.