autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Autotest: enable colored test results.


From: Eric Blake
Subject: Re: Autotest: enable colored test results.
Date: Mon, 14 Jun 2010 11:28:11 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Lightning/1.0b2pre Mnenhy/0.8.2 Thunderbird/3.0.4

On 06/14/2010 11:22 AM, Eric Blake wrote:
> On 06/13/2010 12:50 AM, Ralf Wildenhues wrote:
>> The logical next step for Autotest to be on par with Automake's
>> parallel-test.
>>
>> Unlike Automake, the testsuite author does not have to do anything for
>> the user to be able to use color; AT_COLOR_TESTS only changes the
>> default to yes.  We could easily let it accept an optional argument, if
>> you think it is useful.
> 
> I'm debating whether:
> 
> AT_INIT([testsuite])
> AT_COLOR_TESTS
> 
> vs.
> 
> AT_INIT([testsuite], [color])
> 
> looks nicer.  But keeping it as a separate macro for now seems okay.

Furthermore, keeping it as a separate macro is essential for
conditionally using the feature with a new enough autoconf, without
penalizing use of older autoconf (as witnessed by your recent patch
submission to libtool[1]).  So if we decide to make it an optional
argument of AT_INIT, that should be an independent patch at a later
date, and we should still keep AT_COLOR_TESTS present.

[1] http://lists.gnu.org/archive/html/libtool-patches/2010-06/msg00052.html

-- 
Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]