Re: GNU Wget 1.7 is released
On 14 Jun 2001 22:43:17 +0200, Hrvoje Niksic [EMAIL PROTECTED] wrote: I downloaded wget-1.7, when I tried to configure it, I received an error. I found the error was in ltconfig, because the variable `ORIGINAL_CONFIG_SHELL' was not set. Setting this variable outside the if solved the problem. The diff is below. What system are you using? I find it curious that nobody else has reported this. It is on Red Hat 6.0 Linux, which is kind of old (current RH version is 7.1). I use bash 2.03.01. I will upgrade, but not too soon. I am loathe to change `ltconfig' because it is maintained outside Wget. However, since the upgrade to the next libtool release is scheduled for after 1.7.1, I might apply your patch as a stop-gap fix. If nobody else has encountered this problem, then may be something is wrong with my system/bash. Ehud. -- Ehud Karni Mivtach - Simon Insurance /"\ Tel: +972-3-6212-757 Fax: +972-3-6292-544 \ / ASCII Ribbon Campaign (USA) Fax and voice mail: 1-815-5509341X Against HTML Mail Better Safe Than Sorry / \ mailto:[EMAIL PROTECTED]http://www.simonwiesel.co.il
Re: GNU Wget 1.7 is released
On 04 Jun 2001 21:47:05 +0200, Hrvoje Niksic [EMAIL PROTECTED] wrote:
GNU Wget 1.7 has been released. It is available from
ftp://ftp.gnu.org/pub/gnu/wget/wget-1.7.tar.gz and mirrors of that
site (see list of mirror sites at http://www.gnu.org/order/ftp.html).
I downloaded wget-1.7, when I tried to configure it, I received an
error. I found the error was in ltconfig, because the variable
`ORIGINAL_CONFIG_SHELL' was not set. Setting this variable outside
the if solved the problem. The diff is below.
Ehud.
cd /wget-1.7/
diff -c /wget-1.7/ltconfig.org /wget-1.7/ltconfig
*** /wget-1.7/ltconfig.org Sat Mar 17 16:21:00 2001
--- /wget-1.7/ltconfig Thu Jun 14 16:15:07 2001
***
*** 96,101
--- 96,104
done
IFS="$save_ifs"
+ ORIGINAL_CONFIG_SHELL="${CONFIG_SHELL-/bin/sh}"
+ export ORIGINAL_CONFIG_SHELL
+
if test "X$echo" = Xecho; then
# We didn't find a better echo, so look for alternatives.
if test "X`(print -r '\t') 2/dev/null`" = 'X\t'
***
*** 105,112
elif (test -f /bin/ksh || test -f /bin/ksh$ac_exeext)
test "X$CONFIG_SHELL" != X/bin/ksh; then
# If we have ksh, try running ltconfig again with it.
- ORIGINAL_CONFIG_SHELL="${CONFIG_SHELL-/bin/sh}"
- export ORIGINAL_CONFIG_SHELL
CONFIG_SHELL=/bin/ksh
export CONFIG_SHELL
exec "$CONFIG_SHELL" "$0" --no-reexec ${1+"$@"}
--- 108,113
Diff finished at Thu Jun 14 18:14:29
--
Ehud Karni Mivtach - Simon Insurance /"\
Tel: +972-3-6212-757 Fax: +972-3-6292-544 \ / ASCII Ribbon Campaign
(USA) Fax and voice mail: 1-815-5509341X Against HTML Mail
Better Safe Than Sorry / \
mailto:[EMAIL PROTECTED]http://www.simonwiesel.co.il
Re: GNU Wget 1.7 is released
Ehud Karni [EMAIL PROTECTED] writes: On 04 Jun 2001 21:47:05 +0200, Hrvoje Niksic [EMAIL PROTECTED] wrote: GNU Wget 1.7 has been released. It is available from ftp://ftp.gnu.org/pub/gnu/wget/wget-1.7.tar.gz and mirrors of that site (see list of mirror sites at http://www.gnu.org/order/ftp.html). I downloaded wget-1.7, when I tried to configure it, I received an error. I found the error was in ltconfig, because the variable `ORIGINAL_CONFIG_SHELL' was not set. Setting this variable outside the if solved the problem. The diff is below. What system are you using? I find it curious that nobody else has reported this. I am loathe to change `ltconfig' because it is maintained outside Wget. However, since the upgrade to the next libtool release is scheduled for after 1.7.1, I might apply your patch as a stop-gap fix.
Wget 1.7 is released
Wget 1.7 is now available at ftp.gnu.org:/pub/gnu/wget/. I will announce the release at info-gnu and freshmeat in a few minutes. Please send bug reports to [EMAIL PROTECTED]. There have been no user-visible changes since the last pre-release. A lot of stuff has been added since the release 1.6, which was the last stable release. * Changes in Wget 1.7. ** SSL (`https') pages now work if you compile Wget with SSL support; use the `--with-ssl' configure flag. You need to have OpenSSL installed. ** Cookies are now supported. Wget will accept cookies sent by the server and return them in later requests. Additionally, it can load and save cookies to disk, in the same format that Netscape uses. ** Keep-alive (persistent) HTTP connections are now supported. Using keep-alive allows Wget to share one TCP/IP connection for many retrievals, making multiple-file downloads faster and less stressing for the server and the network. ** Wget now recognizes FTP directory listings generated by NT and VMS servers. ** It is now possible to recurse through FTP sites where logging in puts you in some directory other than '/'. ** You may now use `~' to mean home directory in `.wgetrc'. For example, `load_cookies = ~/.netscape/cookies.txt' works as you would expect. ** The HTML parser has been rewritten. The new one works more reliably, allows finer-grained control over which tags and attributes are detected, and has better support for some features like correctly skipping comments and declarations, decoding entities, etc. It is also more general. ** meta name=robots tags are now respected. ** Wget's internal tables now use hash tables instead of linked lists where appropriate. This results in huge speedups when retrieving large sites (thousands of documents). ** Wget now has a man page, automatically generated from the Texinfo documentation. (The last version that shipped with a man page was 1.4.5). To get this, you need to have pod2man from the Perl distribution installed on your system.
Re: Wget 1.7 is released
On Mon, Jun 04, 2001 at 09:28:50PM +0200, Hrvoje Niksic wrote: Wget 1.7 is now available at ftp.gnu.org:/pub/gnu/wget/. I will announce the release at info-gnu and freshmeat in a few minutes. Please send bug reports to [EMAIL PROTECTED]. There have been no user-visible changes since the last pre-release. A lot of stuff has been added since the release 1.6, which was the last stable release. * Changes in Wget 1.7. ** SSL (`https') pages now work if you compile Wget with SSL support; use the `--with-ssl' configure flag. You need to have OpenSSL installed. ** Cookies are now supported. Wget will accept cookies sent by the server and return them in later requests. Additionally, it can load and save cookies to disk, in the same format that Netscape uses. ** Keep-alive (persistent) HTTP connections are now supported. Using keep-alive allows Wget to share one TCP/IP connection for many retrievals, making multiple-file downloads faster and less stressing for the server and the network. Only for HTTP? Only for recursive? ** Wget now recognizes FTP directory listings generated by NT and VMS servers. ** It is now possible to recurse through FTP sites where logging in puts you in some directory other than '/'. ** You may now use `~' to mean home directory in `.wgetrc'. For example, `load_cookies = ~/.netscape/cookies.txt' works as you would expect. ** The HTML parser has been rewritten. The new one works more reliably, allows finer-grained control over which tags and attributes are detected, and has better support for some features like correctly skipping comments and declarations, decoding entities, etc. It is also more general. ** meta name=robots tags are now respected. ** Wget's internal tables now use hash tables instead of linked lists where appropriate. This results in huge speedups when retrieving large sites (thousands of documents). ** Wget now has a man page, automatically generated from the Texinfo documentation. (The last version that shipped with a man page was 1.4.5). To get this, you need to have pod2man from the Perl distribution installed on your system. -- Always hardwire the explosives -- Fiona Dexter quoting Monkey, J. Gregory Keyes, Dark Genesis
Re: Wget 1.7 is released
toad [EMAIL PROTECTED] writes: ** Keep-alive (persistent) HTTP connections are now supported. Using keep-alive allows Wget to share one TCP/IP connection for many retrievals, making multiple-file downloads faster and less stressing for the server and the network. Only for HTTP? Only for recursive? Note that the above text representes changes relative to 1.6. Wget has always reused FTP connection when you issued something like `wget -r ftp://huge-site.com/'. This was not the case with HTTP. For HTTP it would reconnect over and over for each tiny HTML file, image, whatever. Now, if the HTTP server supports Keep-Alive, Wget will reuse existing HTTP connection for further requests to the same server. This will happen regardless of whether recursion is used. Therefore, these two URLs should share the same HTTP connection: wget http://somesite/file1.html http://somesite/file2.html This does not work for FTP yet.
