Diabetes Simulator wrote:
Hi there. I am new to this list (and wget) but would be grateful
for any advice that anyone may be able to provide.
In particular I have two questions:
(1) Does it matter which server wget is run on (original host vs
mirror?) - or does it need to be run
Karl Eichwalder [EMAIL PROTECTED] writes:
And yes, to re-release a package on account of late translations
is a good idea. I'll answer later in detail. But I don't think
it's a good idea to separate all translations from the main package;
The strategy of re-releasing the whole package
Hrvoje Niksic [EMAIL PROTECTED] writes:
The strategy of re-releasing the whole package shares many of the
flaws with the strings freeze strategy. Specifically, I would be
tempted to include bug fixes and string changes into such a
re-released package.
Would be okay with me. Just increase
Karl Eichwalder [EMAIL PROTECTED] writes:
Would be okay with me. Just increase the version number (reserve the
first 3 numbers for programming realated issue and the 4th number for
translations):
1.7 The normal forthcoming release.
Then
1.7.0.1 Only translations
On 3 Jun 2001, Hrvoje Niksic wrote:
This is what I call additional burden to the maintainer. He has to
roll out another full release, announce it, etc., only because of the
translations.
Consing up a translation tarball is a considerably simpler operation.
Much smaller possibility of
R.I.P. Deaddog [EMAIL PROTECTED] writes:
Actually not many software other than wget can benefit this
way. Other software needs to have ALL_LINGUAS changed if any new
translation is added. Wget is using a combination of ls and sed for
ALL_LINGUAS, but that doesn't work trivially with all
Karl Eichwalder [EMAIL PROTECTED] writes:
It doesn't really. The files I get through the Translation Project
are more a burden than a help for me. They always come too late and I
don't know what to do with them.
Several files for 1.7-pre1 were processed the last 2 or 3 days.
I didn't
Some time ago I came across this web-site with HTTPS connection
problems:
$ wget -S https://www.ihi.dk/
--23:34:50-- https://www.ihi.dk/
= `index.html'
Connecting to www.ihi.dk:443... connected!
Unable to establish SSL connection.
Unable to establish SSL connection.
$
Hrvoje Niksic [EMAIL PROTECTED] writes:
Maybe a more in-depth investigation is needed? I really don't see a
single reason why the ls/sed trick Wget employs shouldn't work for any
other Autoconf-based tool.
Using wildcards is inherently dangerous. I think all source files and
all
