Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , 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 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 13 May 2002 20:34:57 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Pavel Tsekov" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4DAZ8C27837 > -----Original Message----- > From: Pavel Tsekov [mailto:ptsekov AT syntrex DOT com] > Sent: Monday, May 13, 2002 7:53 PM > To: Pavel Tsekov > Cc: cygwin-apps AT cygwin DOT com > Subject: Re: URL paths in setup.exe > > > This thread got stalled... Is there still interest in it ? > How should I change the URL code so I can proceed to finally > submitting this patch for review ? I want to submit it ASAP > so the new code can get some testing... Ensure that it can handle both relative and absolute paths for urls. Something like object.relativePath (baseUrl = ) which returns an empty string (or throws an exception) if object is not able to be made relative to baseUrl (ie different schemes, different authorities) and returns a relative path that can be passed to CreateFile when the tricial call object.relativePath() is made. Also follow through on the file:d|/foo discussion, the | is correct as David has confirmed. As for leading // or not, I'm not fussed... Perhaps, if you could fill out the cygfile: and file: representations of : /foo/bar /cygdrive/g/foo/bar g:\foo\bar Rob