Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24258 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18048 invoked by uid 1010); 3 Jul 2006 23:52:01 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 18033 invoked from network); 3 Jul 2006 23:52:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Jul 2006 23:52:01 -0000 X-PHP-List-Original-Sender: gwynne@skytag.com X-Host-Fingerprint: 208.97.132.61 sd-green-bigip-61.dreamhost.com Linux 2.4/2.6 Received: from ([208.97.132.61:34230] helo=spunkymail-a15.dreamhost.com) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 40/44-13848-0ADA9A44 for ; Mon, 03 Jul 2006 19:52:01 -0400 Received: from [192.168.1.101] (c-24-147-151-210.hsd1.ma.comcast.net [24.147.151.210]) by spunkymail-a15.dreamhost.com (Postfix) with ESMTP id 17D847F031 for ; Mon, 3 Jul 2006 16:51:57 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <44A9B7AD.502@developersdesk.com> References: <952E8F04-87DB-4925-8F08-B999DE354D65@skytag.com> <44A9B7AD.502@developersdesk.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: <3A0FCD44-B118-48B2-AD9C-8055EFA0AE91@skytag.com> Content-Transfer-Encoding: 7bit Date: Mon, 3 Jul 2006 19:51:49 -0400 To: internals@lists.php.net X-Mailer: Apple Mail (2.752.2) Subject: Re: [PHP-DEV] Configure summary From: gwynne@skytag.com (Gwynne) On Jul 3, 2006, at 8:34 PM, Rick Widmer wrote: >> I was poking around at the TODO and I saw this: >> * make configure print out a summary when it's done (like XEmacs) >> 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? 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 would say it should list every option that the user can select, > and show its value. For extra credit, on each entry tell if the > value is the default - either set to the default value, or not > specified. The general consensus seems to be that I should show as much info as is reasonably possible. For this, extensions need to be able to register the summary information they can provide. I've come up with a couple of different ideas for the syntax on this: 1) Add a new parameter to PHP_NEW_EXTENSION(), i.e.: PHP_NEW_EXTENSION(standard, array.c base64.c basic_functions.c browscap.c crc32.c # \ etc, ,,,, \ [Standard functions Regex type:--with-regex=${REGEX_TYPE}]) 2) AC_DEFUN() a new macro, i.e.: PHP_SUMMARY_INFO([Standard functions], [Extension: Enabled Regex type: --with-regex=${REGEX_TYPE}]) These are just random examples based on the standard extension, obviously. Anyone like either of these or have a better idea? -- Gwynne, Daughter of the Code "This whole world is an asylum for the incurable."