You may notice that most shell and Perl script starts with the following line:
It is called a shebang. It consists of a number sign and an exclamation point character (#!), followed by the full path to the interpreter such as /bin/bash. All scripts under Linux, *BSD, macOS, and Unix-like system execute using the interpreter specified on a first line. However, there is a small problem. BASH or Perl is not always in the same location (PATH) such as /bin/bash or /usr/bin/perl. If you want to make sure that script is portable across different UNIX like operating systems you need to use /usr/bin/env command as shebang.
Make Linux/Unix Script Portable With #!/usr/bin/env As a Shebang
The env command allows to run a program in a modified environment. First, find line
For example here is a small bash shell script:
#!/usr/bin/env bash x=5 y=10 echo "$x and $y"
The advantage of #!/usr/bin/env bash is that it will use whatever bash executable appears first in the running user’s $PATH variable. If you have two version of bash installed as follows and PATH set to /home/vivek/bin:/usr/local/bin:/usr/bin:/bin:/usr/games/bin:/bin:/usr/bin, than bash4 will execute the script:
- /bin/bash # <-- bash3
- /usr/local/bin/bash # <-- bash4
#!/usr/bin/env perl use warnings; print "Hello " x 5; print "\\n";
#!/usr/bin/env python x=10 y=20 z=x+y print z
Another example with python3:
#!/usr/bin/env python3 import boto3 t = boto3.resource('s3') for b in t.buckets.all(): print(b.name)
Is env always located at /usr/bin/env
env is /usr/bin/env
Some info from various *nix systems:
ShellCheck is a static analysis tool for shell scripts. One can use it to finds bugs in your shell scripts. It is written in Haskell. You can find warnings and suggestions for bash/sh shell scripts with this tool. Let us see how to install and use ShellCheck on a Linux or Unix-like system to enhance your shell scripts, avoid errors and productivity.
I just made my Linux/Unix script portable with #!/usr/bin/env. The env-mechanism is hugely enhancing convenience, and almost all Unix like systems today provide /usr/bin/env. I regular use FreeBSD, CentOS/RHEL/Ubuntu/Debian/SUSE Linux, macOS, and OpenBSD and all of them provided /usr/bin/env by default. Now you do not have to search for a program via the PATH environment variable. It makes the script more portable. Also, note that it is not a foolproof method. Always make sure you have /usr/bin/env exists or use a soft link/symbolic link to point it to correct path for env command. Moreover, your work or script looks more professional with this simple hack.