Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!teknowledge-vaxc!sri-unix!ctnews!pyramid!uccba!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon Allbery)
Newsgroups: comp.sources.d
Subject: Re: "unportable" shar scripts (Was: A Quick "How-To")
Message-ID: <5191@ncoast.UUCP>
Date: Wed, 4-Nov-87 20:59:28 EST
Article-I.D.: ncoast.5191
Posted: Wed Nov  4 20:59:28 1987
Date-Received: Sun, 8-Nov-87 11:57:41 EST
References: <787@uokmax.UUCP> <4945@ncoast.UUCP> <1815@ho95e.ATT.COM> <228@papaya.bbn.com>
Reply-To: allbery@ncoast.UUCP (Brandon Allbery)
Followup-To: comp.sources.d
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 19

As quoted from <228@papaya.bbn.com> by rsalz@bbn.com (Rich Salz):
+---------------
| Someone complained about seeing
| 	PATH=/bin:/usr/bin:/usr/ucb ; export PATH
| in shar scripts, particularly calling out comp.sources.unix.  He asks if
| it's a standard shar that's doing this, and would prefer to see
| 	PATH=/bin:/usr/bin:/usr/ucb:$PATH ; export PATH
+---------------

On ncoast, I install bugfixed programs in /u/local and chmod -x the original
in order to insure that an upgrade of the OS which doesn't fix the buggy
program doesn't lose the fixed version.  (Case in point: lorder.)  While I
admit that most shar scripts don't run lorder, what would happen if our
version of some commonly-used program (i.e. sed) were to reveal a bug, and
I placed a fixed version in /u/local?  (Not that I could in that case, as we
aren't a source site and rewriting sed from scratch doesn't appeal.)
-- 
Brandon S. Allbery		     necntc!ncoast!allbery@harvard.harvard.edu
 {harvard!necntc,well!hoptoad,sun!mandrill!hal,uunet!hnsurg3}!ncoast!allbery