X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <AANLkTimYqk=ia4opfeH5zycZhwDU6agB7tzWkc3aUKGc@mail.gmail.com>
References: <AANLkTi=98+M5sAsGp4vT09UN9uisqp0M=mgJi9WcSObG AT mail DOT gmail DOT com>	<4D27316D DOT 7070009 AT redhat DOT com>	<AANLkTimYqk=ia4opfeH5zycZhwDU6agB7tzWkc3aUKGc AT mail DOT gmail DOT com>
Date: Sun, 9 Jan 2011 10:13:01 +0100
Message-ID: <AANLkTi=HO3WgV437Jj4NFdK_9oXQ18pG7BoB2YENEbPv@mail.gmail.com>
Subject: Re: Please don't resolve native symbolic links in cygwin_conv_path
From: Reini Urban <rurban AT x-ray DOT at>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

2011/1/7 Daniel Colascione:
> On Fri, Jan 7, 2011 at 7:29 AM, Eric Blake  wrote:
>> On 01/06/2011 06:39 PM, Daniel Colascione wrote:
>>> If a POSIX path supplied to cygwin_conv_path ends in a symbolic link,
>>> the returned path refers to the target of that link. Normally, that's
>>> a good thing because native programs can't understand Cygwin links.
>>> But this behavior is unwanted when we're looking at a *native*
>>> symbolic link that all programs can understand. It's needlessly
>>> specific and rather surprising, and is causing trouble with a program
>>> I'm writing that manipulates native symbolic links.
>>
>> Is this something where we should add a new CCP_ flag to
>> cygwin_conv_path's what argument that allows the user the choice between
>> following or stopping at native symlinks?
>
> I don't see why --- if the caller wants a fully-resolved path, he can
> call realpath() on it before converting it. The Cygwin conversion
> functions should only resolve paths to the minimum extent required for
> interoperability --- the facility is more general and useful that way.

It might be slower but I tend to agree with Dan here.
Current behaviour is annoying. esp. when I use
native symlinks to avoid spaces in paths and then I get them in again.

But I could live also with a new option, which I would use as default in perl.
-- 
Reini Urban

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