Path: utzoo!mnetor!uunet!husc6!uwvax!rutgers!clyde!cbosgd!mandrill!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon Allbery)
Newsgroups: comp.sources.d
Subject: Re: File headers on shar files
Message-ID: <6367@ncoast.UUCP>
Date: 8 Dec 87 02:20:18 GMT
References: <393@ddsw1.UUCP>
Reply-To: allbery@ncoast.UUCP (Brandon Allbery)
Followup-To: comp.sources.d
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 29

As quoted from <393@ddsw1.UUCP> by karl@ddsw1.UUCP (Karl Denninger):
+---------------
| I therefore propose that in the future, when sources (or any other 'shar'
| file) is posted, that the powers that be place any needed 'introduction'
| that preceeds the shar into the file in such a way that it will not
| interfere with the attempts of myself (and I bet others as well) to automate
| or simplify this unpacking.  This can be assured by simply insuring that the
| first character of each line is a "#", making it a shell comment line.
| 
| Thanks for listening! (comments?)
+---------------

Comment 1:  Go ahead, make the Net's day... force me to edit EVERY submission
I get.

Comment (of sorts) 2:

: uns -- unpack shell archives (named or on stdin)
if test -z "$*"; then set x -; shift 1; fi
for arg in "$@"; do
	echo "shar: unpacking ${arg}"
	sed -e '1,/^[:#]/d' "$arg" | sh
done

It never met a "shar" it didn't like.  ;-)
-- 
Brandon S. Allbery		      necntc!ncoast!allbery@harvard.harvard.edu
 {hoptoad,harvard!necntc,cbosgd,sun!mandrill!hal,uunet!hnsurg3}!ncoast!allbery
			Moderator of comp.sources.misc