A tiny fix to the documentation. OK for maint?
Regards, Stefano -*-*- docs: automake testsuite doesn't use TESTS_ENVIRONMENT anymore * doc/automake.texi (Simple Tests): Do not give the example of a TESTS_ENVIRONMENT usage by saying it's what the Automake package itself does: this is not true anymore since it switched to the parallel-tests driver. --- ChangeLog | 8 ++++++++ doc/automake.texi | 5 +++-- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 0fe17ab..1ce8cfd 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,11 @@ +2011-01-17 Stefano Lattarini <stefano.lattar...@gmail.com> + + docs: automake testsuite doesn't use TESTS_ENVIRONMENT anymore + * doc/automake.texi (Simple Tests): Do not give the example of a + TESTS_ENVIRONMENT usage by saying it's what the Automake package + itself does: this is not true anymore since it switched to the + parallel-tests driver. + 2011-01-16 Stefano Lattarini <stefano.lattar...@gmail.com> tests: remove useless requirements from cond36.test diff --git a/doc/automake.texi b/doc/automake.texi index 73c0e51..e50c845 100644 --- a/doc/automake.texi +++ b/doc/automake.texi @@ -8596,8 +8596,9 @@ variables for the test run; the environment variable @env{srcdir} is set in the rule. If all your test programs are scripts, you can also set @code{TESTS_ENVIRONMENT} to an invocation of the shell (e.g. @samp{$(SHELL) -x} can be useful for debugging the tests), or any other -interpreter. For instance the following setup is used by the Automake -package to run four tests in Perl. +interpreter. For instance the following setup was used by the Automake +package@footnote{Before it switched to the use of the +@option{parallel-tests} option.} to run four tests in Perl. @example TESTS_ENVIRONMENT = $(PERL) -Mstrict -I $(top_srcdir)/lib -w TESTS = Condition.pl DisjConditions.pl Version.pl Wrap.pl -- 1.7.2.3