These three have no upstream Linux binary to point at, but also no
equivalent in the AUR or the official repositories - so unlike the packages
dropped in 46ddf59 they can legitimately exist, just as source packages.
bazaar-bin -> bazaar
timetable-bin -> timetable
chromium-widevine-helper-bin -> chromium-widevine-helper
bazaar and timetable now build their meson projects in build(); the
checksum-only CI path still applies, since the source is upstream's release
tarball.
chromium-widevine-helper compiles nothing (Python script, JSON manifests and
extension assets). Upstream publishes neither releases nor tags, so the
package pins the main commit carrying the version from the Fedora spec and
verifies the two agree in prepare() - being tied to a specific version, it
needs no -git suffix. refresh_checksums() moves the pin.
The AUR repos for the new names are created by the first push; the old -bin
packages are left to the pending deletion requests.
update-package.sh no longer builds anything or publishes GitHub release
assets: every package now tracks an upstream deliverable, so the only work
left on a new version is pkgver + checksums. BUILD_DEPS survives for the
CI test build of packages that compile in the PKGBUILD.
Removes the seven packages that cannot be made compliant: upstream ships no
Linux binary to point at, and a maintained source package for each already
exists in the AUR, so a rebuilt version would just be a duplicate.
gearlever-bin, gnome-network-displays-bin, librepods-bin, planify-bin,
protonplus-bin, thonny-bin, trayscale-bin
README documents the rule and why, so the pattern does not come back.
Upstream moved to an "ow" electron-updater channel with a filename
suffix; latest_version checks both channels (vercmp picks the winner) and
refresh_checksums keeps the _appimage filename in sync. Also clean up
downloaded .AppImage files like the other source leftovers.
Felitendo