X-Spam-Check-By: sourceware.org
Message-ID: <457F1CA6.8DBB9F58@dessent.net>
Date: Tue, 12 Dec 2006 13:18:30 -0800
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: library paths
References: <1165944511 DOT 12358 DOT ezmlm AT cygwin DOT com> <200612122106 DOT kBCL68Hc001649 AT sd DOT skydive1 DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Richard Foulk wrote:

> We use perl a lot and are looking into building a standard routine for
> the beginning of each script that will add to the path where necessary.
> And perhaps even remove from the path if two or more instances of the
> key libraries are found.

I don't understand how this would work at all, assuming you mean using
Cygwin's perl.  If the PATH is not set to include /bin then you won't
even be able to run perl at all, let alone execute anything at the
beginning of the script.  The only way to do this would be if you're
talking about CMD.EXE batch file scripting, or some other non-Cygwin
scripting language like VBscript.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/