Concat (https://github.com/jub0t/Concat) is a Tauri 2 shell around a Rust
video engine, sold as a CapCut replacement. The project is mid-rename: the
binary, the desktop entry, the icons and the .deb asset all still say
WolfCut, so the packages install upstream's paths unchanged and add a
/usr/bin/concat symlink.
Upstream stages a static ffmpeg/ffprobe pair (180 MB) and whisper-cli
inside its bundle so the app runs on a machine with nothing installed.
Both lookups fall back to PATH, so concat-bin drops those two directories
and the source packages set WOLFCUT_SYSTEM_TOOLS=1 - the switch upstream
put in build.rs for exactly this case - leaving ffmpeg and whisper-cpp to
Arch. That is 17 MB installed instead of 225 MB.
!lto is not optional: makepkg's lto puts -flto=auto into CFLAGS, and ring
compiles hand-written assembly through cc, which then comes out as bitcode
and links to nothing.
sherpa-onnx-sys ships no C++ build; its build script downloads a prebuilt
static-lib archive. concat lists that archive as a checksummed source and
points the build script at it, with the version read out of upstream's
Cargo.lock by pkg.sh. concat-git cannot pin it - the version moves with
main - so there the build script fetches it.
Every upstream release is a v<version>-alpha.<n> prerelease published on a
push to main, several a day, and the release list is ordered by creation
rather than by version, so the newest is picked by publication date.
Only concat-git is published for now; concat and concat-bin are held back
with AUR_PUBLISH=false until that cadence has been lived with.
Source package built from the release tag and a VCS package following
main, both from :ui:createDistributable - the same jpackage application
image that nextcloud-native-bin repackages from upstream's .deb.
nextcloud-native-git is not version-tracked: its pkgver comes from
pkgver() at build time, so latest_version() reports the snapshot already
in the PKGBUILD and the update run stays a no-op until the packaging
itself changes.
Nextcloud Native (https://github.com/Obiente/nc-native), an adaptive native
Nextcloud client built with Kotlin/Compose Multiplatform. Upstream publishes a
jpackage .deb per release, which the PKGBUILD repackages unchanged.
Every upstream release is a prerelease and the release list is dominated by
per-build nightly-* releases plus rolling channel-* pointers, so pkg.sh tracks
only the versioned v* tags and syncs the build-numbered asset name along with
the checksum.
The description listed the technologies it happens to cover, which reads
like a compatibility list and dates the moment something new turns up. What
it actually does is enable autoscroll wherever that is possible.
Middle-click autoscroll for every Chromium-based application on the system -
Electron and CEF applications, Chromium-based browsers, Flatpaks, Spotify and
Steam - plus anything installed later. Built from source out of the upstream
release tarball, like cachy-auto-update.
Source package for https://github.com/Felitendo/bt-volume-step: a daemon that
corrects the coarse internal volume grid of Bluetooth audio devices on
PipeWire. Nothing is compiled; the upstream Makefile installs the script and
a systemd user unit.
The AUR rejected the push - "package already provided by [extra]: bazaar".
Upstream 0.9.1 landed in the official repositories, which rules the package
out of the AUR entirely, so the source-package conversion from 0229020 has
nowhere to go. Nothing to replace it with: pacman -S bazaar.
README now lists the official repositories as the first thing to check.
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
Felitendo