Changes to gnats/doc/p-inst.texi

[Yngve Svendsen]

Index: gnats/doc/p-inst.texi
diff -c gnats/doc/p-inst.texi:1.22 gnats/doc/p-inst.texi:1.23
*** gnats/doc/p-inst.texi:1.22  Fri Oct 25 03:58:09 2002
--- gnats/doc/p-inst.texi       Sun Oct 27 07:43:36 2002
***************
*** 23,29 ****
  (version 4.2 or higher).  Both are available from the @sc{gnu} FTP site at
  @url{ftp://ftp.gnu.org}.
  
! To build @sc{gnats}, you must:
  
  @itemize @bullet
  @item
--- 23,29 ----
  (version 4.2 or higher).  Both are available from the @sc{gnu} FTP site at
  @url{ftp://ftp.gnu.org}.
  
! To build and install @sc{gnats}, you must:
  
  @itemize @bullet
  @item
***************
*** 59,89 ****
  daemon}.
  
  @item
! Update the local configuration files
! 
! @smallexample
! dbconfig       categories            submitters
! responsible    gnatsd.user_access    states
! classes        addresses
! @end smallexample
! 
! in @address@hidden@var{DATABASEDIR}/gnats-adm}}, as well as the files
! 
! @smallexample
! gnatsd.host_access    databases
! @end smallexample
! 
! in @address@hidden@var{SYSCONFDIR}/gnats}} (usually
! @address@hidden/usr/local/etc/gnats}}).
! 
! @item
! If there are people outside your organization who will be submitting PRs
! or who are supposed to be able to query and/or edit PRs, you may need to
! instruct them to obtain and build the GNATS tools @code{query-pr},
! @code{edit-pr} and @code{send-pr} for their systems.  However, for many
! sites, setting up a remote access interface to GNATS, such as Gnatsweb
! is a better solution since this requires no configuration on the remote
! side.
  @end itemize
  
  @menu
--- 59,71 ----
  daemon}.
  
  @item
! If there are people outside your organization who will be submitting
! PRs or who are supposed to be able to query and/or edit PRs, you may
! need to instruct them to obtain and build the @sc{gnats} tools
! @code{query-pr}, @code{edit-pr} and @code{send-pr} for their systems.
! However, for many sites, setting up a remote access interface to
! @sc{gnats}, such as Gnatsweb is a better solution since this requires
! no configuration on the remote side.
  @end itemize
  
  @menu
***************
*** 231,239 ****
  @item address@hidden@var{path}}
  Set global (across all databases) gnatsd user access file to
  @var{path}. Default is
! @address@hidden/gnats/gnatsd.user_access}.  Per-database user access
! permissions are set in a @file{gnatsd.user_access} file in the
! @file{gnats-adm} subdirectory of each database.
  
  @cindex --with-gnatsd-host-access-file
  @item address@hidden@var{path}}
--- 213,221 ----
  @item address@hidden@var{path}}
  Set global (across all databases) gnatsd user access file to
  @var{path}. Default is
! @address@hidden/usr/local/etc/gnats/gnatsd.user_access}}.  Per-database
! user access permissions are set in a @file{gnatsd.user_access} file in
! the @file{gnats-adm} subdirectory of each database.
  
  @cindex --with-gnatsd-host-access-file
  @item address@hidden@var{path}}
***************
*** 860,870 ****
  @sc{gnats} 3 databases.
  
  @item
! Edit the @sc{gnats} @file{databases} file, located in
! @address@hidden/gnats}.  In a default @sc{gnats} 4 installation
! this is @address@hidden/usr/local/etc/gnats}}.  Add entries for all your old
! @sc{gnats} 3 databases.  @xref{databases file,,The @file{databases}
! file}.
  
  @item
  In @sc{gnats} 3, the file @file{gnatsd.conf} specifies minimum access
--- 842,851 ----
  @sc{gnats} 3 databases.
  
  @item
! Edit the @sc{gnats} @file{databases} file and add entries for all your
! old @sc{gnats} 3 databases.  In a default @sc{gnats} 4 installation
! the file is in @address@hidden/usr/local/etc/gnats}}.  @xref{databases
! file,,The @file{databases} file}.
  
  @item
  In @sc{gnats} 3, the file @file{gnatsd.conf} specifies minimum access