Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24256
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=frbZ4VQSrT+yyZ8opTgHyUy/MbVKarKCrDGT3zEsb3I9/ZjLaA0H8RDRXcqiidWtS8Oodp8sm+nLUmEJuQ70Ph7Q/25dgBnT9i9gtb6xVD456tts9GoV5iy8Q6ELGKB9YfNv3ygHMraOvhG0E2ogBS8KoSXSqdKwYfumKZ/Rlds=
Message-ID: <fe05d1540607031524w7c4804beqc880bff0bde8d070@mail.gmail.com>
Date: Tue, 4 Jul 2006 00:24:05 +0200
To: Gwynne <gwynne@skytag.com>
Cc: internals@lists.php.net
In-Reply-To: <DEFF421A-E1EE-442B-BFA5-5B424F23AC1F@skytag.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <952E8F04-87DB-4925-8F08-B999DE354D65@skytag.com>
	 <fe05d1540607031509h55826dc9ve20301737f17ab40@mail.gmail.com>
	 <DEFF421A-E1EE-442B-BFA5-5B424F23AC1F@skytag.com>
Subject: Re: [PHP-DEV] Configure summary
From: pierre.php@gmail.com (Pierre)

On 7/4/06, Gwynne <gwynne@skytag.com> wrote:
> 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.

The output of configure is useless unless you redirect it to a file
and check everything you are looking for. A summary of this form is
used is many project. There is no need to be very verbose, only saying
what is enabled is already enough.

> Maybe this is something that would only be provided by my --with-
> summary=extended switch?

It should be on by default. I don't count how many times I have had to
run configure again and again because I mis read the output or log :)

> 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.

We already do it anyway with the configure line itself (--with-myext
or --enable-myext, or any other configure option), adding such thing
is a one shot job.

> 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?

I have to check again these macros, but the summary is not very
detailed, it is really only a summary of the enabled features :)

--Pierre