If "#!/usr/bin/env foo" is the preferred #shebang (for portable scripts) in order to find "foo" independent of its path, why isn't the recommended shebang "#!env foo" which would not assume a path for "env" either? 🤔
@publicvoit The kernel interpretes shebang and does not search at all, either the path is exact or it fails to start. Once env is up and running, env does the search along PATH to find foo.
So in fact you want to be sure all those other OSes just dont accept your scripts out of the box ? - Whereas they would have if you used /usr/bin/env foo ?
I say this because I use everyday such an OS, which I think is 10/15 years in advance on the rest of all others linuxes regarding package management and dependencies
Honestly, it is just a remark, not shaming, I will no longer think about it in one minute
@stphrolland@publicvoit
> I use everyday such an OS, which I think is 10/15 years in advance on the rest of all others linuxes regarding package management
You can just say ‘NixOS’, you know.
But IIRC, NixOS in its own packages always rewrites the #! line in scripts to point directly to an executable under /nix/store, so what I recommend isn’t really much different from what it is doing natively.
@publicvoit I had been under the impression that its location was defined by POSIX, like /bin/sh, so didn’t need to be searched. But it seems that’s not true for either one.
However for Unix systems in the real world, having those two utilities in those locations is so commonplace that it feels a lot safer to rely on it than with, for example, Python or even Bash.
Add comment