Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From:	ericblake AT comcast DOT net (Eric Blake)
To:	cygwin AT cygwin DOT com
Subject:	Re: Regression in 1.5.14 cygpath
Date:	Mon, 04 Apr 2005 14:39:43 +0000
Message-Id:	<040420051439.29177.425151AF0004C1DA000071F922069984990A050E040D0C079D0A@comcast.net>
X-Authenticated-Sender:	ZXJpY2JsYWtlQGNvbWNhc3QubmV0

> To be useful, cygpath must fully resolve a pathname, not just the last 
> component.

While I'm at it, it would be nice if cygwin exported resolvepath(2) - it is not POSIX, but Solaris defines it as:

#include <unistd.h>
int resolvepath(const char *path, char *buf, size_t bufsiz);

similar to the POSIX XSI-required realpath(2), but with a size argument.  Coreutils currently checks at configure time for resolvepath, rather than realpath.




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

- Raw text -