• MonkderZweite@feddit.ch
    link
    fedilink
    arrow-up
    21
    ·
    edit-2
    1 year ago

    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.

    • wolo@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      1
      ·
      1 year ago

      #!/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@programming.dev
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        1 year ago

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

          • MonkderZweite@feddit.ch
            link
            fedilink
            arrow-up
            5
            ·
            edit-2
            1 year ago

            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?

            • The Liver@lemm.ee
              link
              fedilink
              arrow-up
              2
              ·
              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

    • quantenzitrone@feddit.de
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

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