You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Publish the Gentoo overlay, and stop winget pointing at a file that does not exist
Gentoo turns out not to need anyone's review. An overlay is a git repo laid out
the way portage expects, so it is ours to push like the tap and the bucket, not a
pull request into someone else's tree. profullstack/gentoo-tronbrowser now exists
with net-misc/tronbrowser-bin 3.15.1, and carries its own write deploy key
(GENTOO_OVERLAY_SSH_KEY). It is a complete overlay: metadata/layout.conf and
profiles/repo_name included, both of which gentoo-pairux is missing, so portage
can actually consume this one.
The ebuild is entirely ${PV}/${P}, so a release needs no edits to its contents --
only the filename carries the version. The templater renames it and drops the
stale one, instead of printing a note and leaving tronbrowser-bin-0.1.1.ebuild in
the tree forever. The Manifest is generated: portage wants BLAKE2B and SHA512
next to the byte count rather than the sha256 every other channel uses, and
node's blake2b512 is byte-identical to b2sum. It names the tarball by the
${P}.tar.gz that SRC_URI renames it to, not by the release asset's filename.
winget is a different story and the blocker is the artifact, not the manifest.
tronbrowser-win-x64.zip contains no tronbrowser.exe at all: the Windows entry
point is tronbrowser.cmd, a shim that hunts for Python 3.9+ and then drives a
copy of Ungoogled Chromium the user must install separately. A portable winget
package around that would install for somebody and then fail to start, so it
would be rejected on review or, worse, accepted and broken. The manifest pointed
RelativeFilePath at that non-existent exe; corrected to the file that does exist,
with the real blocker written down. PairUX ships a nullsoft .exe and is in
winget-pkgs today, which is the shape to copy when someone does the Windows build.
Verified against the live overlay: running the submitter for real reports
"already current, nothing to push", which is only true because the generated
Manifest matches the one computed by hand with b2sum and sha512sum byte for byte.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments