Node:Configure and make, Next:Installing utils, Up:Installation
tar
file which was compressed using gzip
. The code can be extracted
into a directory unpackdir using
cd unpackdir gunzip gnats-4.0-prebeta2.tar.gz tar xvf gnats-4.0-prebeta2.tar
The sources reside in a directory called gnats-4.0-prebeta2
when unpacked. We call this the top level of the source
directory, or srcdir. The sources for the GNATS tools are in
the subdirectory gnats-4.0-prebeta2/gnats/*
. Lists of files
included in the distribution are in each directory in the file
MANIFEST
.
You may wish to alter the installation directory for the Emacs lisp
files. If your Emacs lisp library is not in
prefix/share/emacs/site-lisp
, edit the file
srcdir/gnats/Makefile.in
. Change the variable
lispdir
from prefix/emacs/site-lisp
to the
directory containing your Emacs lisp library. For information on
prefix, see prefix.
gnats
user. You can actually name this
user whatever you want to, as long as it is a valid username on your
system, but we strongly recommend that you call the user gnats
.
If you do decide to give it some other name, remember to use the option
--with-gnats-user
when running configure
below. Below, we
will anyway refer to this user by the name gnats
.
This user must have an entry in the file /etc/passwd
. As for
ordinary users, create a standard home directory for the gnats
user. The default PATH
for this user should contain
exec-prefix/bin
and
exec-prefix/libexec/gnats
. The exec-prefix value
is configurable with the --exec-prefix
configure option described
below, but for standard installations, these two directories correspond
to /usr/local/bin
and /usr/local/libexec/gnats
.
configure
. You can nearly always run configure
with
the simple command
./configure
and the "Right Thing" happens:
/usr/local
(see Where GNATS lives).
/usr/local/com/default
, unless you invoke the utilities with
-d
databasename or --directory=
databasename, or
set the GNATSDB environment variable to point to some other database.
The most common options to configure
are listed below:
configure [ --prefix=prefix ] [ --exec-prefix=exec-prefix ] [ --with-gnats-service=service-name ] [ --with-gnats-user=username ] [ --with-gnatsd-user-access-file=path ] [ --with-gnatsd-host-access-file=path ] [ --with-gnats-dblist-file=path ] [ --with-gnats-default-db=path ] [ --with-kerberos ] [ --with-krb4 ] [ --verbose ]
--prefix=prefix
/usr/local
. See Where GNATS lives.
--exec-prefix=exec-prefix
--with-gnats-service=service-name
--with-gnats-user=username
--with-gnatsd-user-access-file=path
/usr/local/etc/gnats/gnatsd.user_access
. Per-database
user access permissions are set in a gnatsd.user_access
file in
the gnats-adm
subdirectory of each database.
--with-gnatsd-host-access-file=path
/usr/local/etc/gnats/gnatsd_host.access
. There is currently
no way to specify host access permissions on a per-database basis.
--with-gnats-dblist-file=path
Default is prefix/etc/gnats/databases
.
--with-gnats-default-db=path
-d
or --databasename
option, and when the
GNATSDB envrionment variable hasn't been set. Default is
/prefix/com/gnatsdb
.
--with-kerberos
--with-krb4
--verbose
configure
runs.
configure
supports several more options which allow you to
specify in great detail where files are installed. For a complete list
of options, run ./configure --help
in the source directory.
You can build GNATS in a different directory (objdir) from the
source code by calling the configure
program from the new
directory, as in
mkdir objdir cd objdir srcdir/configure ...
By default, make
compiles the programs in the same directory
as the sources (srcdir).
make
, then run
make all info
from the directory where configure
created a Makefile
(this is objdir if you used it, otherwise srcdir.) These
targets indicate:
all
info
info
files using makeinfo
.