VETO
There must be a text/plain file in the top-level source directory
named README that gives the basic information. There should be a
short BUGS file, and possibly a short BETA file, but they can both be
incorporated into README. README.packages can go, as it has by now
served its purpose (or perhaps never served it very well at all).
README need not be all that long, but it MUST give a short blurb
describing the program, (at least for now) describing the unbundled
packages, a description of the basic install process:
tar xzf xemacs.tar.gz
cd xemacs
./configure --prefix=PREFIX ...
make
make check
[on some platforms chown root:mail lib-src/movemail; chmod g+s lib-src/movemail]
make install
cd PREFIX/lib
test ! -d xemacs && mkdir xemacs
cd xemacs
tar xzf xemacs-sumo-DATE.tar.gz
[optionally tar xzf xemacs-mule-sumo-DATE.tar.gz]
and a pointer to INSTALL, a brief mention that it is beta and a
pointer to beta.info/.texi, and the bug report address and a pointer
to the information about reporting bugs in text/more-or-less-readable
as well as the Info or web docs.
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.