ANNOUNCE:  The packaging utilities.

As promised earlier, an almost complete working version of the 
packaging utilities is now available.  To get the most out of
it, you need the following three files:

pkgsrc.taz		V0l2N7
pkgdoc.taz		V0L5N49
samples.taz

pkgsrc.taz contains the source.  A simple make will suffice.  You should
get no warnings at all.  You can then install with 'make install'.

pkgdoc.taz contains the documentation for the standard.  It contains two
files, one is a Word For Windows V2 document, and the other is postscript
output.  This has been specially sized so that it will fit on both US 
letter and A4.  It is 26 pages long.  It can also be previewed with
ghostscript or ghostview.

samples.taz contains a set of four sample packages.  They can all be tried
and tested without installing anywhere useful (ie you can install them all
in /tmp).  On uncompressing and untarring it, you will find the top level
directory has a Makefile.  If you execute it, the four packages will then
be built.  You can then play with the package commands.  The sample packages
are:

	- x picture and animation viewers (binaries only)
	- 8 sample jpeg's (needs above)
	- ps (source and binaries for kernel 0.98pl4+)
	- xvt - efficient xterm replacement - source and binary

Bugs:  I have found one bug in the C library - getgrnam appears to
       take the gid number modulus 32000.  Hence if you have a group
       with an id 320001, the files will be installed with id 1.

       The TODO file in the package source lists what still needs to
       be done - basically pkgchk and the required type for map files.

       The man page needs to be tidied up, and several created that point
       to the page for 'pkg'.  ie pkgadd.1 should point to pkg.1.  Can
       someone who knows anything about man pages please do this for me,
       as I haven't got a clue.  I would also appreciate the main man
       page being tidied up.

       The text printed by pkgadd and pkgrm seems to need more line feeds
       to make it clearer - if anyone has a useful set of ideas or guidelines
       I would like to hear them.

Comments:  I would appreciate any form of comments on the utilities and
       documentation.  I am not emotionally involved with it, so you can say 
       what you want, and  won't be offended/upset etc.  Particularly relevant
       are ways of improving any aspect of the products.  Feel free to post it
       to the mailing list if you don't think everyone will agree with you, or
       to discuss it further.

       I do use source code control, so the source I see, and what you see are
       slightly different.  Please don't make large patches, as they have to be
       applied with manual intervention.

       To make life easier for all concerned, also keep track of the version
       string for each product.  We will all then know which version you are
       talking about.

Help:  If you are having trouble with the utilities, feel free to mail me or the
       list.  If you would like to produce a package, and need some assistance, or
       even someone to do it from .tar.Z files, I am quite prepared to do so.

Roger Binns (cs89rdb@brunel.ac.uk)