Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24255
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
In-Reply-To: <fe05d1540607031509h55826dc9ve20301737f17ab40@mail.gmail.com>
References: <952E8F04-87DB-4925-8F08-B999DE354D65@skytag.com> <fe05d1540607031509h55826dc9ve20301737f17ab40@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <DEFF421A-E1EE-442B-BFA5-5B424F23AC1F@skytag.com>
Cc: internals@lists.php.net
Content-Transfer-Encoding: 7bit
Date: Mon, 3 Jul 2006 18:16:50 -0400
To: Pierre <pierre.php@gmail.com>
Subject: Re: [PHP-DEV] Configure summary
From: gwynne@skytag.com (Gwynne)

On Jul 3, 2006, at 6:09 PM, Pierre wrote:
>> I'm working on a patch to bring in this functionality, out of sheer
>> "I need to learn more about autoconf and I want to contribute to  
>> PHP"-
>> ness :). Does anyone have any thoughts on what might go into such a
>> summary?
> Something like:
>
> GD Support Yes
>  Bundled
>  PNG Yes
>  JPEG No
>  GIF R/W Yes
>
> PDO Support Yes
> PDO Mysql Yes
> PDO Sqlite Bundled Yes
> ...
>
> Maybe with the version found and used, but it could make the summary
> unreadable :)

The problem I have with this is that all of that information is  
already findable from the configure output. Yes, you have to look for  
it, but the idea of a summary is to summarize, not give extensive  
details and basically duplicate all the AC_MSG_CHECKING output. Maybe  
this is something that would only be provided by my --with- 
summary=extended switch?

>> So far, I have install prefix, SAPI, debug on/off, things of
>> that simple nature. Also, any thoughts on whether the summary should
>> be printed from configure itself or config.status?
> I think it may require some additional macros. These macros can be
> called from the extension to set the key/value pairs to display.

I had this thought, but I wasn't really looking to do something  
that'd require changing every config.m4 file in the PHP hierarchy.  
Obviously this would be optional for any given extension, but still,  
it's a larger job than I'm fully confident I can do.

> Good luck and don't hesitate to harass the list until you get it
> working, this is something I was waiting for since way too long (and
> being lazy ;)

Well in that case, perhaps someone can tell me whether I should be  
displaying this information from configure itself (configure.in  
AC_MSG_RESULT macros) or from config.status (init_cmds in  
AC_OUTPUT) :). If it's available from config.status, maybe that'd be  
another reason to provide the very detailed output you suggested above?

-- Gwynne, Daughter of the Code
"This whole world is an asylum for the incurable."