3 ms·
Unless you've actually tested it with a shell other than bash, you should be marking it as bash. Otherwise it's likely it will not actually be portable between
by slavik81 11y ago
Unless you've actually tested it with a shell other than bash, you should be marking it as bash. Otherwise it's likely it will not actually be portable between shells, and you will have made your software less reliable.
I've encountered many scripts written by developers on Fedora that totally fail over when run on Ubuntu specifically due to using #!/bin/sh when they really required #!/bin/bash.
- stephenr 11y agoUnless you've tested it as a shell script you should be marking it as a recipe for a banana cream pie. I specifically said "Write clean, posix-compliant shell scripts" Do the same developers write Java code in a .cpp file and wonder why it doesn't work? Or put <?php tags in a .erb template? Yes, you need to test to make sure that you wrote the correct things.