Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!mcnc!ecsvax!dukeac!bet
From: bet@dukeac.UUCP (Bennett Todd)
Newsgroups: comp.sources.wanted
Subject: Re: Looking for shar
Keywords: shar, cshar
Message-ID: <1319@dukeac.UUCP>
Date: 27 Mar 89 16:45:10 GMT
References: <5140@bnrmtv.UUCP> <1662@arctic.nprdc.arpa>
Reply-To: bet@dukeac.UUCP (Bennett Todd)
Distribution: usa
Organization: Radiology, Duke Med. Center, Durham, NC
Lines: 23

Yikes! 25K and more of sharchive, to distribute a shar program! No doubt, for
someone running a major distribution operation the extensive features would be
worthwhile... But for those of us who rarely if ever try to make our shar
utility handle subdirectories, binary files, mailer length limits, or any of
the other amusing perversions you can hack around, allow me to offer the
following:

: shar -- make a shell archive of the files from the command line
echo ": This is a sharchive -- extract the files by running through sh."
for f
do
	echo "echo x - $f"
	echo "sed 's/^X//' <<\Shar_Eof >$f"
	sed 's/^/X/' <$f
	echo "Shar_Eof"
done
echo "exit 0"

Don't try to pack subdirectories, don't try to pack files containing arbitrary
non-text data, and manually invoke shar separately on sets of files each
smaller than your transmission limit, and this will serve just fine.

-Bennett