Re: Configure summary
| From: | Rasmus Lerdorf | Date: | Mon, 03 Jul 2006 22:53:23 +0000 |
| Subject: | Re: Configure summary | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-24257@lists.php.net to get a copy of this message | ||
Pierre wrote:
On 7/4/06, Gwynne <gwynne@skytag.com> wrote:I would agree with Pierre here. A nice compact summary of what was actually found and where it was found would be what I would expect from this. -RasmusOn Jul 3, 2006, at 6:09 PM, Pierre wrote: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 :)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?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.