Re: overriding tested automake & aclocal in test suite

[Derek R. Price]

Tom Tromey wrote:

> >>>>> "Derek" == Derek R Price <address@hidden> writes:
>
> Derek> Is there some reason the automake test suite doesn't allow the
> Derek> user to override its AUTOMAKE & ACLOCAL variables?  I like to
> Derek> do it on ocassion to compare the current behavior against my
> Derek> installed version and the like.
>
> No, there's no reason.  Send a patch...

Attached.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden         CollabNet ( http://collab.net )
--
I will not carve gods.
I will not carve gods.
I will not carve gods...

          - Bart Simpson on chalkboard, _The Simpsons_


Index: defs
===================================================================
RCS file: /cvs/automake/automake/tests/defs,v
retrieving revision 1.23
diff -u -r1.23 defs
--- defs        2001/03/04 21:05:09     1.23
+++ defs        2001/03/23 21:30:05
@@ -71,7 +71,7 @@
 # See how Automake should be run.  We put --foreign as the default
 # strictness to avoid having to create lots and lots of files.  A test
 # can override this by specifying a different strictness.
-AUTOMAKE="$PERL ../../automake --amdir=$srcdir/.. --foreign"
+: ${AUTOMAKE-"$PERL ../../automake --amdir=$srcdir/.. --foreign"}
 
 # See how aclocal should be run.
-ACLOCAL="$PERL ../../aclocal --acdir=$srcdir/../m4"
+: ${ACLOCAL-"$PERL ../../aclocal --acdir=$srcdir/../m4"}