Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: autoconf 2.5 (Re: PATCH: terminfo horor)
- X-seq: zsh-workers 19352
- From: Oliver Kiddle <okiddle@xxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxxxxx>
- Subject: Re: autoconf 2.5 (Re: PATCH: terminfo horor)
- Date: Thu, 08 Jan 2004 17:11:48 +0100
- In-reply-to: <66F451E8923A3D42B22434287141E2E3D12323@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <66F451E8923A3D42B22434287141E2E3D12323@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author