The AUR does not allow packages to ship a binary tarball built by the
maintainer - a -bin package must repackage a deliverable published by
upstream. These six packages now do that:
snapx-bin upstream's self-contained Linux tar.zst
zapzap-bin upstream's pure-Python wheel
faugus-launcher-bin upstream's arch-independent .deb
wiiudownloader-bin upstream's AppImage
waydroid-helper-bin upstream's AppImage
chiaki-ng-bin upstream's AppImage
All six drop build_artifact() and switch to refresh_checksums(), so CI no
longer builds or hosts anything - it only tracks upstream's assets.
Where the asset name carries build metadata that does not follow from
pkgver (snapx, faugus-launcher), refresh_checksums() resolves it via the
GitHub API and syncs an _asset variable in the PKGBUILD.
Dependency lists are re-derived from what the bundles actually resolve
outside themselves; the AppImage payloads land in /opt with wrappers in
/usr/bin, because their entry points resolve paths relative to argv[0].
Artifact rebuilds (e.g. dependency bundling) change the file behind
<pkg>-<ver>.tar.zst while keeping its name, so users with the previous
file in their AUR helper cache hit a checksum mismatch. Naming the local
download <pkg>-<ver>-<rel>.tar.zst makes every rebuild a fresh file.
Felitendo
github-actions[bot]
Felitendo