From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] wget2
Date: Fri, 27 Nov 2020 11:28:48 -0700 [thread overview]
Message-ID: <8a1948e9-7789-50a0-dd37-fb474f876476@SystematicSw.ab.ca> (raw)
In-Reply-To: <DB7PR02MB3996087423CE6FD6703E9856E7F80@DB7PR02MB3996.eurprd02.prod.outlook.com>
On 2020-11-27 10:57, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 24/11/2020 21:06, Brian Inglis wrote:
>> On 2020-07-08 14:05, Brian Inglis wrote:
>>> wget2 is the successor of wget supplying a shared library API like
>>> curl to
>>> build a modern, fast, multi-threaded, parallel downloader using
>>> HTTP/2, HTTP
>>> compression and If-Modified-Since headers; see:
>>> https://gitlab.com/gnuwget/wget2
>>> It is currently available on Arch, Debian/Ubuntu, openSUSE,
>>> Slackware; see:
>>
>> https://repology.org/project/wget2/versions
>>
>> Thanks for help getting here and also the upstream folks!
>>
>> Please review wget2 repackaged into subpackages available under:
>>
>> https://drive.google.com/drive/folders/1VVuC14KuB6uShm4FQL9BuXH0hpLYnIcJ?usp=sharing
>>
>>
>> Appveyor CI playground repo wget2 jobs:
>>
>> https://cygwin.com/cgi-bin2/jobs.cgi?id=1308
>>
>> I have been dogfooding wget2 instead of wget in commands and cron jobs
>> and it appears considerably faster, but does not support FTP or other
>> protocols supported by curl or wget, and does not support wget
>> --retr-symlinks=no option which retrieves symlink contents verbatim
>> for analysis with readlink e.g. wget ...-latest... and see if it
>> points to the previous or a newer version.
>>
>> For more compatibility info see:
>>
>> https://gitlab.com/gnuwget/wget2/-/wikis/home
>
> I had a quick go on 32-bit Cygwin (figuring most people might try
> 64-bit), and it seems to work fine and be quite quick. I haven't
> compiled the package but I'll find time soon hopefully - it's small so I
> guess it doesn't take long.
Thanks - nearly 15min on Appveyor with all the library, devel, and debuginfo
bits involved.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-11-27 18:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 20:05 [ITP] wget2 - modern fast parallel file and recursive website downloader Brian Inglis
2020-07-08 20:28 ` Brian Inglis
2020-07-09 18:27 ` Marco Atzeri
2020-07-09 18:50 ` Yaakov Selkowitz
2020-07-10 1:38 ` Brian Inglis
2020-07-10 5:27 ` Marco Atzeri
2020-10-30 21:30 ` Brian Inglis
2020-10-30 21:34 ` Eric Blake
2020-10-30 21:57 ` [ITA] wget Brian Inglis
2020-10-31 12:50 ` Marco Atzeri
2020-11-14 15:19 ` Achim Gratz
2020-11-14 22:15 ` Brian Inglis
2020-11-15 7:36 ` ASSI
2020-11-15 17:32 ` Brian Inglis
2020-11-16 17:23 ` Achim Gratz
2020-11-16 21:35 ` Brian Inglis
2020-11-17 19:10 ` Achim Gratz
2020-11-17 23:23 ` Brian Inglis
2020-11-18 14:23 ` ASSI
2020-11-10 5:29 ` [ITP] wget2 - please review if anyone has time Brian Inglis
2020-11-24 21:06 ` [ITP] wget2 Brian Inglis
2020-11-27 17:57 ` Hamish McIntyre-Bhatty
2020-11-27 18:28 ` Brian Inglis [this message]
2020-11-30 14:51 ` Hamish McIntyre-Bhatty
2020-11-30 18:29 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a1948e9-7789-50a0-dd37-fb474f876476@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).