0 Fork 0

Files

T

Felitendo 0229020278 Group C: rebuild as source packages without the -bin suffix

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.

2026-07-27 17:46:36 +02:00

6.5 KiB

Raw Blame History

PKGBUILDS

Automated AUR packages, kept up to date by GitHub Actions.

Every 6 hours the update workflow checks each package's upstream for a new release. When one is found it:

updates the PKGBUILD (pkgver/pkgrel/sha256sums),
test-builds it with makepkg and regenerates .SRCINFO,
commits the changes back to this repository, and
pushes the package files to the AUR.

Ground rule

Nothing is ever built or hosted here. Every PKGBUILD sources a deliverable published by upstream — a release tarball, .deb, wheel or AppImage — exactly like any hand-written AUR package would.

This is not a style preference. The AUR submission guidelines say:

Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix. […] The AUR should not contain the binary tarball created by makepkg

A -bin package repackages what upstream ships. Building the software yourself, publishing the result as a release asset and having the AUR PKGBUILD download that makes this repository an unofficial binary repository — users can no longer verify that the package matches what upstream released. Packages set up that way were removed from the AUR in July 2026; do not reintroduce the pattern.

If upstream ships no Linux binary, there are exactly two options: build from source in the PKGBUILD (and drop the -bin suffix), or don't package it.

Packages

Package	Upstream	Upstream deliverable	AUR
`bazaar`	bazaar-org/bazaar — GNOME app store for flatpaks/Flathub	built from source	bazaar
`chiaki-ng-bin`	streetpea/chiaki-ng — PlayStation Remote Play client (Qt6)	AppImage	chiaki-ng-bin
`chromium-widevine-helper`	GloriousEggroll/chromium-widevine-helper — extension + native helper installing Google's Widevine CDM into Chromium-based browser profiles	no build step	chromium-widevine-helper
`faugus-launcher-bin`	Faugus/faugus-launcher — launcher for Windows games via UMU-Launcher	`.deb` (`all`)	faugus-launcher-bin
`fluxer-bin`	fluxer.app — Fluxer desktop client (Electron)	tarball	fluxer-bin
`lunar-client-bin`	lunarclient.com — Minecraft PvP modpack launcher	AppImage	lunar-client-bin
`modrinth-app-bin`	modrinth/code — Minecraft mod manager/launcher	`.deb`	modrinth-app-bin
`sharpemu-bin`	sharpemu/sharpemu — experimental PlayStation 5 emulator	tarball	sharpemu-bin
`snapx-bin`	SnapXL/SnapX — ShareX-fork screenshot/sharing tool	self-contained tarball	snapx-bin
`timetable`	ostfriese4/untis — "Timetable", a GTK4 + LibAdwaita client for WebUntis	built from source	timetable
`vacuumtube-bin`	shy1132/VacuumTube — YouTube Leanback (TV UI) with built-in adblocker	`.deb`	vacuumtube-bin
`waydroid-helper-bin`	ayasa520/waydroid-helper — GTK4 GUI for Waydroid configuration and extensions	AppImage	waydroid-helper-bin
`wiiudownloader-bin`	Xpl0itU/WiiUDownloader — Wii U title downloader (Go + GTK3)	AppImage	wiiudownloader-bin
`zapzap-bin`	rafatosta/zapzap — WhatsApp desktop client (PyQt6 + WebEngine)	wheel	zapzap-bin

Setup (one-time)

Create an AUR account and add an SSH public key to it (AUR account settings).
Add the matching private key as a repository secret named AUR_SSH_PRIVATE_KEY (Settings → Secrets and variables → Actions → New repository secret).
Optionally set the repository variable AUR_GIT_NAME and the repository secret AUR_GIT_EMAIL to control the commit identity used on the AUR (defaults: Felitendo / the maintainer's GitHub noreply address).

The first push to ssh://aur@aur.archlinux.org/<pkgname>.git creates the AUR package automatically.

Adding a package

Check first that upstream actually publishes a Linux binary and that the AUR does not already carry an equivalent package — a -bin next to a maintained source package is fine, a second copy of the same thing is not.

Then create a directory named after the AUR package containing:

PKGBUILD — sources upstream's release URLs directly. pkgver, pkgrel and sha256sums are maintained by CI, so keep sha256sums on a single line.
pkg.sh — bash sourced by scripts/update-package.sh, defining:
- latest_version — prints the latest upstream version, no v prefix.
- refresh_checksums <version> <pkgbuild-path> — updates the sha256sums* lines for that version. If the asset name carries build metadata that does not follow from pkgver (see snapx-bin, faugus-launcher-bin), resolve it via the GitHub API here and sync an _asset variable in the PKGBUILD too.
- BUILD_DEPS — optional array of Arch packages to install before the CI test build; only needed by packages that build from source.
Other local source files in the directory (.desktop files, patches, …) are pushed to the AUR alongside PKGBUILD and .SRCINFO.

The workflow discovers package directories automatically. Trigger a run manually via Actions → Update AUR packages → Run workflow to publish it immediately.