[comp.os.coherent] Posting sources, how do we do it?

gsm@mailgsm.mendelson.com (Geoffrey S. Mendelson) (04/26/91)

Since it seems that we all agree that source files should be posted,
I think we should agree on a set of standards on how to post them.

Most coherent users are not unix wizzards. They do not have the techincal
skills required to do complicated unpacking. If we agree on a packing
method, anyone who can follow a list of commands could unpack the files.

I am not trying to denigrate anyone, and I hope I have insulted no one. It's
hard to make people think below their level without comming off like an a**h*le 
(asterisks provided to fool cenosring programs).

But we need to think like a new user here.

My recemendations are:

What to post: (in order of importance):

1. Fixed or replaced system modules (may be limited due to copyright)

2. Things that should have been part of the system but aren't, ie a uucp retry 
   routine :-), or an autobauding getty.
   
3. Things that everyone needs. ie. less, smail.

4. Things that everyone wants.


What not to post:

1. Someone-else's copyrighted code (without permission).

2. games.

3. Neat hacks (for example, a coherent version of the Amiga emulator of the 
   Nintendo Gameboy)

4. Stuff that doesn't work. :-)

5. Files over 16k (after uuencoding). 
	This seems like a small limit, but many news systems are overloaded already.
	This should be taken as a suggestion, not a demand. 

6. Compiled modules. Not that I don't trust anyone, but lets keep it to source
   code.

7. Patch files. Most people will have enough trouble with complete files,
   don't confuse them with patches.It's very anoying to download a file
   that you want, only to find out it is a set of patches with no original code.
   
1 and 4 do not belong anywhere, 2 and 3 should be announced, but sent out
via email (if small) or disk (if not) to those who want it.


How to send files:

Small C programs or shell scripts may be included in the posting in source
form.

All other files should be compressed and then uuencoded. The following shell
script "sendme" will do the work for you:

------------------------------------------------------------------------------
#
#  sendme shell script.
#
#  This script will porcess a file for posting in news.
#  The ouput is placed in /tmp/sendfile.
#
# 4/91 Geoffrey S. Mendelson
#
set -xv
if test " $1" = " "
then
	echo "please specify a file."
fi
cp $1 "/tmp/$1"
compress -b  "/tmp/$1"  
uuencode  >/tmp/sendfile "/tmp/$1.Z" "$1.Z"

------------------------------------------------------------------------------- 

To use type:

 sendme FILENAME
 
Include /tmp/sendfile in your article.
------
Geoffrey S. Mendelson 
geoffrey@mendelson.com
(215) 242-8712