From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16621 invoked from network); 8 Jan 2004 16:07:43 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 8 Jan 2004 16:07:43 -0000 Received: (qmail 14219 invoked by alias); 8 Jan 2004 16:07:18 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 19352 Received: (qmail 14171 invoked from network); 8 Jan 2004 16:07:17 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 8 Jan 2004 16:07:17 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [193.109.254.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 8 Jan 2004 16:7:16 -0000 X-VirusChecked: Checked X-Env-Sender: okiddle@yahoo.co.uk X-Msg-Ref: server-9.tower-36.messagelabs.com!1073578030!2988336 X-StarScan-Version: 5.1.15; banners=-,-,- Received: (qmail 6494 invoked from network); 8 Jan 2004 16:07:10 -0000 Received: from iris.logica.co.uk (158.234.9.163) by server-9.tower-36.messagelabs.com with SMTP; 8 Jan 2004 16:07:10 -0000 Received: from gmcs3.local ([158.234.142.61]) by iris.logica.co.uk (8.12.3/8.12.3/Debian -4) with ESMTP id i08G79uB025051 for ; Thu, 8 Jan 2004 16:07:09 GMT Received: from gmcs3.local (localhost [127.0.0.1]) by gmcs3.local (8.11.6/8.11.6/SuSE Linux 0.5) with ESMTP id i08GBml09012 for ; Thu, 8 Jan 2004 17:11:48 +0100 X-VirusChecked: Checked X-StarScan-Version: 5.0.7; banners=.,-,- In-reply-to: <66F451E8923A3D42B22434287141E2E3D12323@mowp006a.ru001.siemens.net> From: Oliver Kiddle References: <66F451E8923A3D42B22434287141E2E3D12323@mowp006a.ru001.siemens.net> To: Zsh hackers list Subject: Re: autoconf 2.5 (Re: PATCH: terminfo horor) Date: Thu, 08 Jan 2004 17:11:48 +0100 Message-ID: <9010.1073578308@gmcs3.local> Andrey wrote: > > right; but to do it we need make configure puts into config.status (or as > init part of running config.modules.sh) information that modules may need to > make decision. Using cache variables was big mistake to start with :( Why do the decisions modules make need to be re-made when config.status runs? Can't we just evaluate decisions once, in configure, and store the answers in config.status? Oliver