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
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 3 Sep 2002 18:48:12 +1000 (EST)
From:	luke DOT kendall AT cisra DOT canon DOT com DOT au
Subject:	Re: How do you write scripts with portable filenames?
To:	Max Bowsher <maxb AT ukf DOT net>
Cc:	cygwin AT cygwin DOT com
In-Reply-To:	<003d01c25325$8cd3a090$0100a8c0@wdg.uk.ibm.com>
MIME-Version:	1.0
Message-Id:	<20020903084809.5D71758A0@ivory.research.canon.com.au>

On  3 Sep, Max Bowsher wrote:
>  I _was_ pretty sure that this was supposed to 'just work'. (And it does with mv, 
>  but not with rm). I guess this is a bug. I think you might be at least 
>  temporarily stuck with using `uname` to find out if you are on cygwin, and 
>  setting and using an EXEEXT variable throughout the script. 

The trouble is when the EXEEXT has toi be a whole set, like .exe or .dll
or .sh or .pl or .awk ... you get the idea.

It's great to know that it should just work; for now I can just modify
the specific script that's causing me a problem, and trust that later
on, things will just work.  So in the future it won't be a problem.

(Fingers crossed.)

luke


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