Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ncoast.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!cwruecmp!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon Allbery)
Newsgroups: net.sources.bugs
Subject: shars
Message-ID: <1157@ncoast.UUCP>
Date: Sun, 27-Apr-86 10:06:31 EDT
Article-I.D.: ncoast.1157
Posted: Sun Apr 27 10:06:31 1986
Date-Received: Thu, 1-May-86 02:42:17 EDT
References: <947@kitty.UUCP> <2407@prls.UUCP> <1439@garfield.columbia.edu> <2555@utcsri.UUCP> <172@gilbbs.UUCP> <1617@wucs.UUCP>
Reply-To: allbery@ncoast.UUCP (Brandon Allbery)
Followup-To: net.sources.bugs
Distribution: net
Organization: North Coast Computer Resources
Lines: 25

Expires:

Quoted from <1617@wucs.UUCP> ["Re: Beware of Blindly Un-SHARing a File"], by tp@wucs.UUCP...
+---------------
|    I've been waiting for someone else to say this...
| 
|    naughtiness in shar files is only the tip of the iceberg. The program
| contained in the shar may do bad things... the makefile that builds the 
| program may do bad things...
| 
|     doesn't have to be anything malicious  -- I see a lot of makefiles
| that would install things where I wouldn't want them or would write over
| something important or were just simply incorrect  (a lot of the same can 
| be said for the shar files; a lot of authors don't seem to anticipate system 
| configurations different from their own).
+---------------

I document any Makefile system-specific install paths; and my version of
``shar'' checks to see if the destination exists:  if it does, it allows you
to overwrite OR rename the to-be-unshar'ed file OR skip the file.

--Brandon
-- 
decvax!cwruecmp!ncoast!allbery  ncoast!allbery@Case.CSNET  ncoast!tdi2!brandon
(ncoast!tdi2!root for business) 6615 Center St. #A1-105, Mentor, OH 44060-4101
Phone: +01 216 974 9210      CIS 74106,1032      MCI MAIL BALLBERY (part-time)
PC UNIX/UNIX PC - which do you like best?  See <1129@ncoast.UUCP> in net.unix.