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: <3C45DB7E.8030105@ece.gatech.edu>
Date: Wed, 16 Jan 2002 14:58:54 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
CC: Eric Blake <ebb9 AT email DOT byu DOT edu>, cygwin AT cygwin DOT com
Subject: Re: devel tool wrappers and --version, --help
References: <3C45D6B3 DOT B4808783 AT email DOT byu DOT edu> <3C45DADF DOT 4070407 AT ece DOT gatech DOT edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Charles Wilson wrote:

> I have already been given a patch to do this, but I am a little 
> concerned about implementation.  It makes sense to me, to defer to the 
> -devel version, but I am concerned about ripple effects...
> 
> IMO, if you are libtoolizing (autoconf'ing, automake'ing) a new 
> directory that has no existing configure.in, then the suggested 
> solutions should be sufficient:
>   create a temporary configure.in that has only "AC_REQUIRE(2.52)"
>    or
>   set path = /usr/autotool/devel/bin
> 
> Setting up the wrapper scripts to report one version or the other -- 
> with no reason to prefer one over the other, such as a pre-existing 
> configure.in file -- is just lying.


Just to make it clear -- I am not opposed to applying the patch to 
effect this behavior, but I am worried about unintended consequences. 
Discussion?

--Chuck



--
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/