Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!sci.ccny.cuny.edu!phri!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.unix.questions
Subject: Re: portability of non-shell scripts
Keywords: portability
Message-ID: <14869@smoke.brl.mil>
Date: 16 Jan 91 01:08:36 GMT
References: <1991Jan15.233523.18150@ux1.cso.uiuc.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 9

In article <1991Jan15.233523.18150@ux1.cso.uiuc.edu> phil@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.