Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site well.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!gatech!ut-sally!seismo!lll-crg!well!dv
From: dv@well.UUCP (David W. Vezie)
Newsgroups: net.sources.bugs
Subject: Re: Re: Could we have a standard "shar" file format?
Message-ID: <314@well.UUCP>
Date: Tue, 3-Dec-85 02:41:55 EST
Article-I.D.: well.314
Posted: Tue Dec  3 02:41:55 1985
Date-Received: Thu, 5-Dec-85 08:10:36 EST
References: <396@persci.UUCP> <4048@amdcad.UUCP> <579@edison.UUCP> <6320@amdcad.UUCP> <185@xios.UUCP>
Reply-To: dv@well.UUCP (David W. Vezie)
Organization: Whole Earth 'Lectronic Link, Sausalito CA
Lines: 32
Keywords: shar format

echo #define notdef >> /usr/include/stdio.h

	Could I propose a "standard" for articles posted to all.sources?
(I realize that by asking, I'm expecting a negative answer... :-).  It
is actually simple:

	1, entire article is a shar file (meaning, all you should have
	   to do is strip off the header and feed to sh).

	2, the order of the files in the shar file are as such:
		a, README - description of what the package contains
			    (this is usually found ABOVE the shar package)
		b, man pages
		c, Makefiles
		d, Header files
		e, Source files

	3, even if it is one file, package it as a shar file with a
	   README.  That way I don't have to use an editor with it,
	   I can just run it through unshar.  It also means that I
	   don't have to save the article itself to have all the
	   information about the software.

	4, use a shell archiver that puts an "exit 0" at the end of
	   the article (before the .signature).


Comments?
--- 
David W. Vezie
	    {dual|hplabs}!well!dv - Whole Earth 'Lectronics Link, Sausalito, CA
(4 lines, 114 chars)