Wget2 change breaks compatibility and should be reverted

Project Discussion
1

this change should be reverted also for backward compatibility… I have lots of scripts that are COMPLETELY broken for this since wget2 command line is not backward compatibile with wget cli…
Please restore the old wget as default wget (an user can install wget2, if it wants to do)

2 Likes
2

This is a planned change. See F40 Change Proposal: wget2 as Wget

There is a link to docs of wget vs wget2 incompatibility in that topic.

2 Likes
3

A post was split to a new topic: Wget versus wget2 | how to fix old scripts

4

I’m thinking about user prospective… User have scripts that always worked and from a release to another release the script stops working without a good reason. Moreover centos-stream-10/RHEL10 still uses wget1 and this adds another layer of incompatibilities without a good reason. Nobody else uses wget2 as default wget, neither Arch Linux that is known to use bleeding edge packages…

2 Likes
5

Feel free to raise a bugzilla ticket about this in the Fedora bug tracker.

1 Like
6

I assume that if it was reverted it will break code that has already been ported in wget2.

1 Like
7

As I recall, the wget codebase was becoming an unmaintable mess, so wget2 was intended to be more maintainable. Are your issues with wget2 due to functionality that was removed (e.g., dropped support for some legacy protocols) or changes in arguments to accomplish a given task?

2 Likes