Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <20011202232134.13585.qmail@web10401.mail.yahoo.com>
Date: Sun, 2 Dec 2001 15:21:34 -0800 (PST)
From: Brett Porter <brettporter AT yahoo DOT com>
Subject: Re: Restructuring the automake and autoconf packages
To: cygwin AT cygwin DOT com
In-Reply-To: <20011202143537.A10634@cygbert.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

I have a couple of questions regarding this (apologies
if already covered - I'm on the digest and only got
this message on announce).

Let's see if I understand correctly:
1. you run autoconf
2. it sets the path based on a wrapper script
3. next execution goes to the desired one directly.

Doesn't this limit you to only running ./configure for
one package within a single bash shell? (or removing
the env. variable/modifying PATH). It sounds like a
good idea for effeciency, but I'm a bit worried about
the confusion factor.

Also, I think you stated the default is autoconf-2.52.
This seems to be back to front as many old
configure.in's might not AC_PREREQ(2.13), whereas
newer ones are probably inclined to AC_PREREQ(2.52)
since the uptake is lower. I'm not sure I'm right on
this, really everyone should request what they want
anyway, but its food for thought.

Good work on this - I think it's a great solution to
the problem for now. A better libtool is worth it.

Cheers,
Brett


__________________________________________________
Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.
http://shopping.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/