|
From: | Gary V. Vaughan |
Subject: | Re: patch-1: testsuite automake version requirements |
Date: | Wed, 14 Dec 2005 10:06:16 +0000 |
User-agent: | Mozilla Thunderbird 1.0 (X11/20050305) |
Hallo Ralf! I'm back in the UK for a few weeks :-D Ralf Wildenhues wrote:
* Ralf Wildenhues wrote on Sun, Dec 04, 2005 at 03:56:15PM CET:I'll be replying to this mail with a number of patches, separated by logical changes, and *should* work in the order posted (I hope). - two patches for compatibility with older Automake*snip* Not really sure about how to handle old Automake versions. The biggest question, testsuite-wise, is whether we should go back to the old AC_INIT AM_INIT_AUTOMAKE(package, release) scheme, and put automake options in Makefile.am's AUTOMAKE_OPTIONS = ... For now I have only done the latter. That way, the mechanism to detect this and flag `expected failure' at least works with the old automake. But this also means that we have very little actual test exposure for versions <1.6. Comments?
Patch looks good by inspection. Maybe we could put the bulk of the tests from testsuite.at inside a loop (oversimplified for explanatory purposes): for AMMINOR in 10 9 8 7 6 5 4; do AUTOMAKE=automake-1.$AMMINOR test -x $AUTOMAKE || continue echo "*** Running testsuite with $AUTOMAKE ***" echo m4_include(*.at) echo done Then any problems with compatibility with older automake APIs should come out in the wash... Cheers, Gary. -- Gary V. Vaughan ())_. address@hidden,gnu.org} Research Scientist ( '/ http://tkd.kicks-ass.net GNU Hacker / )= http://www.gnu.org/software/libtool Technical Author `(_~)_ http://sources.redhat.com/autobook
signature.asc
Description: OpenPGP digital signature
[Prev in Thread] | Current Thread | [Next in Thread] |