commit 79a7ee58bc22cbc92a1e46068e62f7ac643d28a0
Author: lucascouts <lucascs@protonmail.com>
Date: Tue Sep 22 09:10:49 2026 -0300

add(net-misc/wget2-2.3.0, metadata/md5-cache/net-misc/wget2-2.3.0), mod(.autoupdate/packages.toml)

Copy net-misc/wget2 from ::gentoo (2.2.1 as the base) and update it to the
2.3.0 release of 2026-09-21.

The only divergence from the ::gentoo ebuild is the subslot. ::gentoo pins it
at 0 while upstream has shipped libwget.so.4 since 2.2.x, so its subslot never
tracked the soname its own comment names. 2.3.0 raises LIBWGET_SO_VERSION from
4:0:0 to 5:0:0 -> libwget.so.5, an ABI break that must rebuild every := consumer,
so the subslot here carries the real soname. Tagged BENTOO-DIVERGENCE: SLOT.

The configure surface is otherwise unchanged between the two releases: only
--with-linux-crypto went away and --with-gpgme-prefix arrived, and the ebuild
uses neither.

The autoupdate record probes the GNU FTP directory listing, which IS the
SRC_URI source, rather than the GitLab tag space: upstream tags the release
before uploading the tarball, so a tag-based probe would propose a version
whose mirror://gnu distfile does not exist yet. The listing holds every
historical release in name order, hence select = "max".

Verified locally, unprivileged: `ebuild ... clean install` completes, the
installed image carries SONAME libwget.so.5 (confirming the subslot), no .la
and no wget2_noinstall survive src_install, and the built binary downloads
over HTTPS. pkgcheck is clean, gentoo-parity reports 1 row JUSTIFIED / 0 ALIGN,
and the new record round-trips through `bentoo overlay autoupdate --check`.
USE=test, USE=doc and USE=lzip were not exercised.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>