Mailing-List:	contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT cygwin DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT cygwin DOT com>
List-Help:	<mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
Subject:	RE: URL paths in setup.exe
Date:	Tue, 7 May 2002 20:45:33 +1000
MIME-Version:	1.0
Message-ID:	<FC169E059D1A0442A04C40F86D9BA7600C6000@itdomain003.itdomain.net.au>
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
X-MS-Has-Attach:
content-class:	urn:content-classes:message
X-MS-TNEF-Correlator:
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Pavel Tsekov" <ptsekov AT syntrex DOT com>, <cygwin-apps AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g47Ak0419003

I'd like to formalise what file:// and cygfile:// schemes mean.

file:// is a native filesystem URL handler - whatever the OS may be.
cygfile:// is a handler that only makes sense on mingw platforms, and
access's the cygwin mount table.

This means that:
file:///foo/bar.txt is /foo/bar.txt on posix, and Current
drive:\foo\bar.txt on mingw.

As for file:// + d: + \foo\bar.txt, can we normalise that as 
file://d|/foo/bar.txt - that is what MS do, and will be less confusing
for users of the codebase (IMO).

Rob

- Raw text -