This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
RE: URL paths in setup.exe
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Pavel Tsekov" <ptsekov at syntrex dot com>
- Cc: <cygwin-apps at cygwin dot com>
- Date: Mon, 13 May 2002 20:34:57 +1000
- Subject: RE: URL paths in setup.exe
> -----Original Message-----
> From: Pavel Tsekov [mailto:ptsekov@syntrex.com]
> Sent: Monday, May 13, 2002 7:53 PM
> To: Pavel Tsekov
> Cc: cygwin-apps@cygwin.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 = <singleton which
represents file://valueofcwd>) 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
:
<cwd>/foo/bar
/cygdrive/g/foo/bar
g:\foo\bar
Rob