Message-ID: <4B5FF5AE.3050904@users.sourceforge.net>
Date: Wed, 27 Jan 2010 02:13:34 -0600
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Bug: cygport fails when the working directory pathname contains    spaces
References: <4B5FA03C.8020504@monai.ca> <4B5FC41E.6090301@users.sourceforge.net> <4B5FD16E.4060107@monai.ca>
In-Reply-To: <4B5FD16E.4060107@monai.ca>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 26/01/2010 23:38, Steven Monai wrote:
> Imagine if a program like 'cp' failed because the current working
> directory has a pathname that contains spaces. You'd probably agree with
> me that 'cp' had a rather serious flaw, wouldn't you?

cygport is not 'cp'.  cygport is a shell script, as are configure 
scripts, the autoconf-generated kind being the most common build system 
out there.  Shell scripts usually use spaces for IFS.  Hence 
distinguishing between a space in a file name/path and whitespace 
between arguments is fraught with difficulties.

> I stand by my original report. This is a bug. Not a serious show-stopper
> by any stretch, but a bug, nonetheless.
 >
> When I find the time and motivation, I may try my hand at fixing it
> myself. I'll report back with patches if I do.

As the author of cygport, I'll advise you that your time will be much 
better spent getting used to not using spaces in file and directory 
names rather than pretending to "fix" a case that will never be 
guaranteed to work.


Yaakov

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