Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: (setup.ini) autoconf requires Perl?
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0209131135560 DOT 19696-100000 AT slinky DOT cs DOT nyu DOT edu>
From: "Patrick J. LoPresti" <patl AT curl DOT com>
Date: 13 Sep 2002 11:46:46 -0400
In-Reply-To: <Pine.GSO.4.44.0209131135560.19696-100000@slinky.cs.nyu.edu>
Message-ID: <s5gelbxdh95.fsf@egghead.curl.com>
Lines: 24
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu> writes:

> On 13 Sep 2002, Patrick J. LoPresti wrote:
> 
> > P.S. How about renaming Cygwin Perl to "perl" instead of "perl.exe"?
> 
> If you are worried about name clashes, you're better off moving the
> ActivePerl directory to the front of your path (in /etc/profile, for
> example).

No, not really.  ActivePerl and Cygwin Perl are *different* programs.
You know which one you want when you invoke it, not when you set up
your PATH; they really must have different names.

Under your suggestion, the name for ActivePerl would be "perl" and the
name for Cygwin Perl would be "/usr/bin/perl".  This makes it
impossible to write a portable script between Unix (where perl might
really be "/usr/local/bin/perl") and Cygwin.

We don't happen to have any such scripts, so your suggestion works for
us and is what I plan to do.  But it really isn't the "right" answer.
Neither is my suggestion, really, but for different reasons :-).

 - Pat

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