-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Ed wrote:

> On Mac OS X the (sanitised) log output looks like this
> 
> --16:56:33--  http://xx.blogs.com/xx/2007/03/carbon_offsets.html
>            => `/dirnames/xx.blogs.com/prawfsblawg/2007/03/carbon_offsets.html'
> Resolving xx.blogs.com... 1.2.3.4
> Connecting to xx.blogs.com|1.2.3.4|:80... connected.
> 
> On CentOS it looks like this
> 
> --16:50:49--  http://xx.blogs.com/prawfsblawg/2007/03/carbon_offsets.html
> Resolving xx.blogs.com... 1.2.3.4
> Connecting to xx.blogs.com|1.2.3.4|:80... connected.
> 
> Note the line beginning '=>' giving the filename is missing on CentOS,
> unfortunately I was using this for validation. Any idea why there is a
> difference between the 2 platforms? Any idea how I can get the output
> filename shown on all platforms?

This change in format has happened in the current pre-1.11 development
repository. I believe the reason was probably that we can no longer tell
what filename we are going to use at that point, since we honor
Content-Disposition: you'll now see a message like "Saving to `foo'"
instead.

It looks like the Red Hat source RPMs include a patch named
"wget-1.10.2-to11.patch", which brings in a large number of changes that
have been made to wget since 1.10.2. It therefore appears that Red Hat,
along with its derivatives such as CentOS and Fedora, isn't _really_
using wget 1.10.2 at all, but is using something between that and the
current development version.

You might try to obtain an RPM for an older version of Red Hat's RPM:
probably a -1 or -2 release will have minimal changes. Otherwise, you
could always get the official tarball from GNU, and use that instead.

- --
HTH,
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGw1Mv7M8hyUobTrERCO0qAJ0S4MtOgbHFQvAYmuMq3cGXPN/lAACbB97e
i7tOfWJJ5SFoRLG4HLXHLJI=
=cUSb
-----END PGP SIGNATURE-----

Reply via email to