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.
A package can now be prepared in this repository before it goes public:
pkg.sh sets AUR_PUBLISH=false and steps 1-4 run as usual, so the PKGBUILD
is kept current and test-built while the publishing waits.
.tar.bz2 joins the archive types the run cleans up and gitignores; concat
carries one as a source.
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.
Felitendo
github-actions[bot]