From 2c5f2648c94b72cc26b5b1d4dc9dd6642c63c47e Mon Sep 17 00:00:00 2001
From: Alexandre Duret-Lutz <adl@gnu.org>
Date: Tue, 11 Jun 2002 09:12:41 +0000
Subject: [PATCH] * automake.texi (Tests): Document site.exp.  Update DejaGnu's
 url.

---
 ChangeLog     |  4 ++++
 automake.texi | 20 ++++++++++++++------
 2 files changed, 18 insertions(+), 6 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index c4eec051..482bd0eb 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2002-06-11  Alexandre Duret-Lutz  <duret_g@epita.fr>
+
+	* automake.texi (Tests): Document site.exp.  Update DejaGnu's url.
+
 2002-06-10  Alexandre Duret-Lutz  <duret_g@epita.fr>
 
 	* lib/am/header-vars.am (transform): Define.
diff --git a/automake.texi b/automake.texi
index e150d856..feecc293 100644
--- a/automake.texi
+++ b/automake.texi
@@ -4025,12 +4025,11 @@ program.
 
 @section DejaGNU Tests
 
-If @uref{ftp://prep.ai.mit.edu/pub/gnu/dejagnu-1.3.tar.gz,
-@samp{dejagnu}} appears in @code{AUTOMAKE_OPTIONS}, then a
-@code{dejagnu}-based test suite is assumed.  The variable
-@code{DEJATOOL} is a list of names which are passed, one at a time, as
-the @code{--tool} argument to @code{runtest} invocations; it defaults to
-the name of the package.
+If @uref{ftp://ftp.gnu.org/gnu/dejagnu/, @samp{dejagnu}} appears in
+@code{AUTOMAKE_OPTIONS}, then a @code{dejagnu}-based test suite is
+assumed.  The variable @code{DEJATOOL} is a list of names which are
+passed, one at a time, as the @code{--tool} argument to @code{runtest}
+invocations; it defaults to the name of the package.
 
 The variable @code{RUNTESTDEFAULTFLAGS} holds the @code{--tool} and
 @code{--srcdir} flags that are passed to dejagnu by default; this can be
@@ -4055,6 +4054,15 @@ The contents of the variable @code{RUNTESTFLAGS} are passed to the
 @vindex AM_RUNTESTFLAGS
 @c FIXME xref dejagnu
 
+@cindex @file{site.exp}
+Automake will generate rules to create a local @file{site.exp} file,
+defining various variables detected by @code{./configure}.  This file
+is automatically read by DejaGnu.  It is ok for the user of a package
+to edit this file in order to tune the test suite.  However this is
+not the place where the test suite author should define new variables:
+this should be done elsewhere in the real test suite code.
+Especially, @file{site.exp} should not be distributed.
+
 In either case, the testing is done via @samp{make check}.
 
 @section Install Tests
-- 
2.43.5