Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!clyde!cbosgd!gwspc!cbcsta!n8emr!lwv
From: lwv@n8emr.UUCP (Larry W. Virden)
Newsgroups: comp.sources.d
Subject: Re: File headers on shar files
Message-ID: <365@n8emr.UUCP>
Date: Sat, 5-Dec-87 09:14:07 EST
Article-I.D.: n8emr.365
Posted: Sat Dec  5 09:14:07 1987
Date-Received: Thu, 10-Dec-87 20:23:45 EST
References: <393@ddsw1.UUCP>
Reply-To: lwv@n8emr.UUCP (Larry W. Virden)
Organization: N8EMR's Ham BBS (HBBS), Columbus,Ohio
Lines: 25
Keywords: headers, comp.sources, source postings, shars


I would like to suggest one better!  If you have commentary / descriptions /
etc place it in the shar in such a way that it goes into a file!  I find
that often there is useful info in that part that I don't get to see if
I blinkdly unshar the program.

As for the referenced article's proposal, if one is fortunate to be on
a Unix-alike system, it is easy to write up a sed | sh pipe to skip 
everything up to the first line with a # and feed the rest to sh.  Thus,
the newly proposed format isnt need for us.  As for non-unix sites, I would
assume that they already have a C program to unshar the files, since sed
is a product of someone or other attached to ATT/Bell Labs/etc.  

Perhaps the easiest thing to do is for someone to post a copy of a C unshar
that all could use, making the whole discussion a moot point.  If you have
such a creature, would you at least consider putting in an option to save
off the header and other info in to a SHAR.INFO file or something?  That way
I keep the address of the moderator/poster, any pre-shar comments, etc.

Thanks!
-- 
Larry W. Virden	 75046,606 (CIS)
674 Falls Place, Reynoldsburg, OH 43068 (614) 864-8817
cbosgd!n8emr!lwv (UUCP) 	cbosgd!n8emr!lwv@ucbvax.Berkeley.EDU (BITNET)
We haven't inherited the world from our parents, but borrowed it from our children.