		    Installation procedures for GNATS

   *** This is a very brief discussion of the installation procedure ***
   *** for GNATS.  It is strongly recommended that anyone attempting  ***
   *** to install and operate GNATS refer to the file gnats.texi.      ***

Installing GNATS
****************

   *Note Where the tools and utilities reside: Locations.

   There are several steps you need to follow to fully configure and
install GNATS on your system.  You need `root' access in order to
create a new account for `gnats' and to install the GNATS utilities.
You may need `root' access on some systems in order to set up mail
aliases and to allow this new account access to `cron' and `at'.

   If you are updating an older version of GNATS rather than installing
from scratch, see *Note Upgrading from older versions: Upgrading.

   In order to build GNATS, you will need to have GNU `m4' installed;
most systems ship with a version of `m4' that is not able to work with
the `config.m4' file.

   To build GNATS, you must:

   * Run `configure', with correct options if the defaults are
     unsuitable for your site.  *Note Configuring and compiling the
     software: Configure and make.  Default installation locations are
     in *Note Where GNATS lives: Locations.

   * Compile the GNATS programs on your system.  *Note Configuring and
     compiling the software: Configure and make.

   * Install the GNATS tools and utilities locally, and install the user
     tools on every machine in your local network.  *Note Installing
     the utilities: Installing utils.

   * Set up mail aliases for GNATS.  *Note Setting up mail aliases:
     Aliases.

   * Install the GNATS user tools (`query-pr', `nquery-pr', `edit-pr',
     `send-pr') around your network.  *Note Installing the user tools:
     Installing tools.

   * Install the GNATS daemon `gnatsd'.  *Note Installing the daemon::.

   * Update the local configuration files

          config      categories  submitters  responsible  gnatsd.conf

     in `GNATS_ROOT/gnats-adm'.  *Note Changing your local
     configuration: Local configuration.

   * Create a distribution of `send-pr' for submitters outside your
     organization.  *Note Configuring `send-pr' for the outside world:
     mkdist.


