[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

A. Installing send-pr on your system

If you receive send-pr as part of a larger software distribution, it probably gets installed when the full distribution is installed. If you are using GNATS at your site as well, you must decide where send-pr sends Problem Reports by default; see Setting a default site.

A.1 Installing send-pr by itself  installing `send-pr' by itself
A.2 Setting a default site  setting a default site


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

A.1 Installing send-pr by itself

Install send-pr by following these steps (you may need root access in order to change the `aliases' file and to install send-pr):


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

A.2 Setting a default site

send-pr is capable of sending Problem Reports to any number of Support Sites, using mail aliases which have `-gnats' appended them. send-pr automatically appends the suffix, so that when you type

 
send-pr site

the Problem Report goes to the address noted in the `aliases' file as `site-gnats'. You can do this in the Emacs version of send-pr by invoking the program with

 
C-u M-x send-pr

You are prompted for site.

site is also used to error-check the `>Category:' field, as a precaution against sending mistaken information (and against sending information to the wrong site).

You may also simply type

 
send-pr

from the shell (or `M-x send-pr' in Emacs), and the Problem Report you generate will be sent to the site, which is usually the site from which you received your distribution of send-pr. If you use GNATS at your own organization, the default is usually your local address for reporting problems.

To change this, simply edit the file `Makefile' before installing and change the line

 
GNATS_SITE = site

to reflect the site where you wish to send PRs by default.


[ << ] [ >> ]           [Top] [Contents] [Index] [ ? ]

This document was generated by XEmacs shared group account on December, 19 2009 using texi2html 1.65.