X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,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:	<4D27316D.7070009@redhat.com>
References:	<AANLkTi=98+M5sAsGp4vT09UN9uisqp0M=mgJi9WcSObG AT mail DOT gmail DOT com> <4D27316D DOT 7070009 AT redhat DOT com>
Date:	Fri, 7 Jan 2011 13:54:49 -0800
Message-ID:	<AANLkTimYqk=ia4opfeH5zycZhwDU6agB7tzWkc3aUKGc@mail.gmail.com>
Subject:	Re: Please don't resolve native symbolic links in cygwin_conv_path
From:	Daniel Colascione <dan DOT colascione AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

On Fri, Jan 7, 2011 at 7:29 AM, Eric Blake <eblake AT redhat DOT com> 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.

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

- Raw text -