Re: Some test results with current svn version

2007-08-13 Thread Jochen Roderburg
Zitat von Micah Cowan [EMAIL PROTECTED]:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Jochen Roderburg wrote:
  I have tried out again the current wget version from svn to see the
 progress on
  various discussed problems.
 
  Someone recently reported an inability to specify the prefix for libssl.
 
  Hmm, yes, I reported this a year ago  ;-)
 
  That works now again as expected. When I specify
 --with-libssl-prefix=/usr/local
  I get the correct libs in the Makefile(s):

 This has just recently been fixed; it had to do with the fact that we
 were using sh if where we should have been using autoconf AS_IF.
 This has unfortunate interactions with autoconf's mechanisms for
 automated dependency resolution. Sorry I didn't reply to my previous
 message to say so, but I wasn't sure anyone had paid attention to it ;)

And my mail was meant as a confirmation that this fix works  ;-)
(I had seen your previous message about this and saw in the code that something
had been done regarding this issue.)


  I see, however, no difference yet regarding Content-Disposition, despite
 the
  explanations in ChangeLogs and recent mails that there is now an option for
 it
  which is off as default.

 Mauro has just finished some code related to this, so you can try it out
 when that has gone into the trunk. :)


OK, I'll have another look next weekend.

Best Regards,
Jochen Roderburg



Some test results with current svn version

2007-08-12 Thread Jochen Roderburg

I have tried out again the current wget version from svn to see the progress on
various discussed problems.

 Someone recently reported an inability to specify the prefix for libssl.

Hmm, yes, I reported this a year ago  ;-)

That works now again as expected. When I specify --with-libssl-prefix=/usr/local
I get the correct libs in the Makefile(s):

LIBS = -lintl -ldl -lrt  /usr/local/lib/libssl.so /usr/local/lib/libcrypto.so
-Wl,-rpath -Wl,/usr/local/lib


I understand that the HEAD/GET issues are still in discussion and testing, the
current state that I see now is:

no timestamping, no local file   no HEAD
no timestamping,local file   no HEAD
   timestamping, no local file  HEAD
   timestamping,local file  HEAD

(and the file-transfer as such works again).

I see, however, no difference yet regarding Content-Disposition, despite the
explanations in ChangeLogs and recent mails that there is now an option for it
which is off as default.

Best Regards,

Jochen Roderburg
ZAIK/RRZK
University of Cologne
Robert-Koch-Str. 10Tel.:   +49-221/478-7024
D-50931 Koeln  E-Mail: [EMAIL PROTECTED]
Germany