Kyle Andrews <k...@posteo.net> writes: > The (many) shell scripts in my software depend on bashisms. In the code right > now I typically use /usr/bin/env bash since I had read that was the most > portable way of referencing a shell. However, I really don't think I have a > good > handle on what my choices are. Maybe the tedious solution of just typing `bash > script.sh' in all of the system calls referencing this scripts might be the > right approach in the long run?
``/usr/bin/env bash'' will automatically be substituted for the path to an available ``/bin/bash'' in the store. (If that's what you're talking about here; not sure what the context is exactly.)
