The reboot of the wget project just released wget-1.99.2, which will become the new wget2. Supports HTTP/2 and many new things the old wget doesn't support. https://lists.gnu.org/archive/html/info-gnu/2019-09/msg00001.html
Created attachment 589396 [details] wget2-1.99.2.ebuild Unfortunately it does not and will never support FTP :-( So it is not really a drop-in replacement for wget-1
Yes, noticed this when I tried to use it with portage instead of old wget. Perhaps Gentoo should switch to use cURL as default instead if wget-1 isn't going to be maintained. Another option is to have two separate packages net-misc/wget and net-misc/wget2? At least wget-2 really ought to be slotted somehow? Thanks for the ebuild.
I'm replying to myself here. The author of Wget2 writes this on Gitlab: ~~~~ FTPS was never wide-spread and FTP is going to be obsoleted by the "encrypt everything" movement. The two main FTP sites I used (Debian archives + downloads from gnu.org) both offer HTTPS since a while. Of course you will always see single persons using FTP for whatever reason. But hey, there is wget for (recursive) FTP downloads. Before supporting FTP I would rather check files and documentation of any projects (you like/use) for non-HTTPS URLs and make up a MR/PR to fix it. ~~~~ I guess the issue of encryption vs FTP isn't valid for portage since it does its own checksum verification.
(In reply to Gatak from comment #2) > Another option is to have two separate packages net-misc/wget and > net-misc/wget2? The attached ebuild is a separate package. Put it into net-misc/wget2 (In reply to Gatak from comment #3) > I'm replying to myself here. The author of Wget2 writes this on Gitlab: > > ~~~~ > FTPS was never wide-spread and FTP is going to be obsoleted by the "encrypt > everything" movement. The two main FTP sites I used (Debian archives + > downloads from gnu.org) both offer HTTPS since a while. > > Of course you will always see single persons using FTP for whatever reason. > But hey, there is wget for (recursive) FTP downloads. > > Before supporting FTP I would rather check files and documentation of any > projects (you like/use) for non-HTTPS URLs and make up a MR/PR to fix it. > ~~~~ > > I guess the issue of encryption vs FTP isn't valid for portage since it does > its own checksum verification. I find his whole reasoning stupid. Yes FTP is no longer that wide spread compared to https but it's still a valid file transfer protocol and should get supported by wget2 if it is meant to be a drop-in replacement for wget1. If security is of concern, there is FTPS (FTP with TLS) and SFTP (FTP over SSH). Ideally wget2 should support all of these.
It would be great if it was available as a separate "wget2" package, like it's it's done in Debian and derivatives, instead of replacing wget 1.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dc759f10b10848442a41e965cef293978725dbc3 commit dc759f10b10848442a41e965cef293978725dbc3 Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2020-03-08 21:02:26 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2020-03-08 21:02:49 +0000 net-misc/wget2: Initial commit Closes: https://bugs.gentoo.org/693638 Package-Manager: Portage-2.3.93, Repoman-2.3.20 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> net-misc/wget2/Manifest | 1 + .../files/wget2-1.99.2-remove_ldconfig_call.patch | 25 ++++++ net-misc/wget2/metadata.xml | 16 ++++ net-misc/wget2/wget2-1.99.2.ebuild | 91 ++++++++++++++++++++++ 4 files changed, 133 insertions(+)
