autoconf-patches
[Top][All Lists]
Advanced

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

Re: [PATCH 4/4] _AC_OUTPUT_FILES_PREPARE: Rephrase CONFIG_FILES test


From: Bernhard Reutner-Fischer
Subject: Re: [PATCH 4/4] _AC_OUTPUT_FILES_PREPARE: Rephrase CONFIG_FILES test
Date: Thu, 9 Apr 2015 15:31:31 +0200

On 9 April 2015 at 15:22, Eric Blake <address@hidden> wrote:
> On 04/09/2015 06:43 AM, Bernhard Reutner-Fischer wrote:
>> 2015-04-08  Bernhard Reutner-Fischer  <address@hidden>
>>
>>       * lib/autoconf/status.m4 (_AC_OUTPUT_FILES_PREPARE): Rephrase
>>       test for empty CONFIG_FILES.
>>
>> Signed-off-by: Bernhard Reutner-Fischer <address@hidden>
>> ---
>>  lib/autoconf/status.m4 |    2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/lib/autoconf/status.m4 b/lib/autoconf/status.m4
>> index 7ccc847..6a00739 100644
>> --- a/lib/autoconf/status.m4
>> +++ b/lib/autoconf/status.m4
>> @@ -327,7 +327,7 @@ m4_define([_AC_OUTPUT_FILES_PREPARE],
>>  [# Set up the scripts for CONFIG_FILES section.
>>  # No need to generate them if there are no CONFIG_FILES.
>>  # This happens for instance with `./config.status config.h'.
>> -if test -n "$CONFIG_FILES"; then
>> +if [[ ${CONFIG_FILES:+y} ]]; then
>
> Why the ${a:+b} form here, but the ${a+b} form in patch 1?

If CONFIG_FILES is set to an empty string then there's nothing to do i assume.

thanks,



reply via email to

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