Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!bbn!bbn.com!rsalz
From: rsalz@bbn.com (Rich Salz)
Newsgroups: comp.sources.d
Subject: Re: shar - archiver
Message-ID: <1500@papaya.bbn.com>
Date: 16 Feb 89 00:27:55 GMT
References: <8877@orstcs.CS.ORST.EDU>
Distribution: na
Organization: BBN Systems and Technologies Corporation
Lines: 28

In <8877@orstcs.CS.ORST.EDU> bleckmd@jacobs.CS.ORST.EDU (david bleckmann) writes:
>I am looking for a version of shar that basically does everything.
>... break into parts ... uuencode .. keep track of which parts ..

>I have got ahold of cshar, from comp.sources.unix, and as far as I
>can tell, it can't do the uuencoding part.
This is true.  In fact, I think I even pointed out in the README file that
I'm not interested in binary files.

Well, I changed my mind. :-)

The next release of cshar provides a new program, maniscan.  This program
reads a manifest and checks the files named there.  If it finds a binary
file, it uuencodes it.  If it finds a large file, it's split into pieces.
If it finds control characters in a text file, or a long line, or a line
that ends with whitespace (which BITNET hates), a warning message is
printed.  All the warnings are dumped to a logfile or stderr.

The manifest is rewritten to reflect these changes, and the logfile is
appended to the manifest.  You can then run makekit over the new
manifest.

If you've found any bugs in cshar2, patchlevel3, please let me know ASAP.
I hope to put the new version out in alt.sources for alpha test in a
month, then post it in comp.sources.unix
	/rich $alz
-- 
Please send comp.sources.unix-related mail to rsalz@uunet.uu.net.