-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have a question: why do we attempt to generate absolute paths and such
and CWD to those, instead of just doing the portable string-of-CWDs to
get where we need to be? Technically, we can violate the RFCs
(specifically, RFC 1738, which defines the
On Fri, 3 Aug 2007, Micah Cowan wrote:
I have a question: why do we attempt to generate absolute paths and such and
CWD to those, instead of just doing the portable string-of-CWDs to get where
we need to be?
Just a word of caution here: while RFC1738 tells this is the way to do it,
there
Micah Cowan [EMAIL PROTECTED] writes:
I have a question: why do we attempt to generate absolute paths and
such and CWD to those, instead of just doing the portable
string-of-CWDs to get where we need to be?
I think the original reason was that absolute paths allow crossing
from any directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel Stenberg wrote:
On Fri, 3 Aug 2007, Micah Cowan wrote:
I have a question: why do we attempt to generate absolute paths and
such and CWD to those, instead of just doing the portable
string-of-CWDs to get where we need to be?
Just a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Someone recently reported an inability to specify the prefix for libssl.
It seems the culprit is somehow the multiple invocation of the macro
AC_LIB_HAVE_LINKFLAGS, even though they appear in exclusive conditional
sections.
If one removes the
From: Hrvoje Niksic
I agree that string-of-CWDs would be better than the current solution.
Well, that's good news. See, for example, the discussion around:
http://www.mail-archive.com/wget@sunsite.dk/msg08233.html
Also:
http://www.mail-archive.com/wget@sunsite.dk/msg08447.html
On Sat, 4 Aug 2007, Micah Cowan wrote:
Just a word of caution here: while RFC1738 tells this is the way to do it,
there are servers and times where this approach doesn't work. (lib)curl has
an option to specify the CWD style (multiple cwd, single cwd or no cwd) due
to this...
Could you be
