portability of non-shell scripts

[Doug Gwyn]

In article <1991Jan15.233523.18150 at ux1.cso.uiuc.edu> phil at ux1.cso.uiuc.edu (Phil Howard KA9WGN) writes:
>Is there no consitency to this?  Has anyone worked a general way to make
>these script programs more portable so that they will run w/o having to
>have the user do editing on them?

About the best I know of is to ALWAYS use #!/bin/sh and tell that shell
what command to run, with what arguments.  If you set $PATH to a nice,
fairly inclusive set of possible directories then the command should be
found no matter which of the directories it resides in.