bill lam <[email protected]> wrote: > The OS is free to symlink any shell to /bin/sh , eg in MacBook > % /bin/sh --version
Of course. Creating a /bin/sh just to appease the install script is an option. Another option is to sed-replace the script's shebang. However, an env-shebang fixes the cases where those workarounds are needed without breaking anything else to my knowledge. We are probably working with different mental models of "normal systems" here. If you are focused on end-user Linux distributions, then /bin/sh is almost certainly guaranteed to exist and be fine, but since this is a build system script, it is likely to get run under "odd" environments that want to closely control what's on PATH, what the filesystem looks like, etc. Surch "odd" environments do end up often having to resort to hacky workarounds due to non-portable shell scripts, but I see no reason to explicitly *reject* a change with pure portability upsides. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
