Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!smsc.sony.com!dce
From: dce@smsc.sony.com (David Elliott)
Newsgroups: comp.windows.x
Subject: Re: export contrib procedure?
Message-ID: <1991May4.144307.14350@smsc.sony.com>
Date: 4 May 91 14:43:07 GMT
References: <1991Apr25.163621.922@ux1.cso.uiuc.edu> <9104261520.AA05343@expire.lcs.mit.edu>
Organization: Sony Microsystems Corp, San Jose, CA
Lines: 27

In article <9104261520.AA05343@expire.lcs.mit.edu> rws@expo.lcs.mit.EDU (Bob Scheifler) writes:
>
>    What are the procedures/guidelines/rules for contributing software to
>    contrib on export.lcs.mit.edu?
>
>It should be X-related.  It should be in tar format, compressed.
>That's about it.

For those of us on the user end of things, it's nice if the package
contains the following:

	* An Imakefile (if it doesn't, at least be willing to incorporate
	  one of the ones you will certainly receive).  It's best if
	  it can be used with xmkmf to work outside of the X development
	  tree.

	* A README with your email address near the top

	* A manual page (try to use the prefix .man like the other X stuff)

	* A patchlevel.h file that defines PATCHLEVEL

There are a number of us out here that build everything that comes
along, and will be glad to help make your software more portable.  In
my case, the lack of an Imakefile means I either have to write one or I
have to hack the Makefile to add extra libraries and defines to make it
work.