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:	<16ed01c19ed0$42629e30$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
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>
References:	<3C45D6B3 DOT B4808783 AT email DOT byu DOT edu> <3C45DADF DOT 4070407 AT ece DOT gatech DOT edu> <3C45DB7E DOT 8030105 AT ece DOT gatech DOT edu>
Subject:	Re: devel tool wrappers and --version, --help
Date:	Thu, 17 Jan 2002 07:56:23 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime:	16 Jan 2002 20:56:11.0992 (UTC) FILETIME=[3ACC0580:01C19ED0]

===
----- Original Message -----
From: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>


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

There is a problem that isn't addressed: autoscan.

Whatever heuristic is appropriate for autoscan should equally apply to
an empty directory.

I can't think of an appropriate heuristic, but your message
"autoscan: Couldn't find configure.ac nor configure.in file
run /usr/auto*/bin/autoscan directly"
seems reasonable to me. (That is, that the user must explicity choose in
this case).

Rob


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

- Raw text -