llvm22
Dropped, 2026-10-07. Not a package in this tree anymore – forked, built
(3h19m), hand-patched, and published to archlinuxaba on 2026-10-06/07 to
unblock
[odin-git],
then dropped the same day once it turned out official Arch extra already
ships a real llvm22/llvm22-libs (packaged by the actual upstream LLVM
maintainer, built back in September 2026 – pacman -Si llvm22 shows
Repository: extra,
Packager: Leonidas Spyropoulos <artafinde@archlinux.org>). All of this
package’s work was redundant; nothing here needed inventing.
The miss: before forking, checked AUR’s RPC search API for llvm22/similar
version-pinned packages (found only llvm17, llvm19) and checked pkgctl’s
packaging history for the official llvm package’s own prior versions – but
never checked whether extra itself already had a separate,
already-existing llvm22 package under that exact name. pacman -Ss llvm22 or
pacman -Si llvm22 directly would have caught this in seconds, before any of
the build/patch/import work below. Lesson: when hunting for a version-pinned
compat package, check the official repos for that exact name directly – don’t
assume “the official package is at version X” means “there’s no official compat
package at version Y under a different name.”
What actually happened (for the record)
- Forked official
llvm’s packaging history at the last 22.x commit (7f8e185, viapkgctl repo clone+git log), repackaged under a versioned prefix (/usr/lib/llvm22,/usr/bin/<tool>-22) to coexist with the systemllvm. Built successfully, 3h19m. - Hit two real packaging bugs after publish (3 bare
.sosymlinks and/usr/bin/litcolliding with the systemllvm/llvm-libs) – fixed via a hand-repack of the already-built archives rather than a second 3h rebuild (user-approved shortcut). - Imported the official package’s full git history (215 commits) into a
standalone repo at
arch/maintained/llvm22with one commit on top for the repackaging, intending to push it to AUR as a genuinely new submission. - User found the pre-existing
extra/llvm22independently and asked to drop everything: the local history-backed repo (rm -rf arch/maintained/llvm22), and the published packages fromarchlinuxaba– removed from the repo db (repo-remove) and deleted from bothos/x86_64/andarchive/x86_64/on the repo host (the latter is normally append-only, see [[feedback_archive_append_only]], but explicitly overridden here by direct user instruction for this cleanup). odin-git’smakedependsalready just saidllvm22by package name (no repo pin) – no PKGBUILD change needed there beyond fixing a comment that referenced the now-deletedmaintained/llvm22. Rebuilt clean againstextra/llvm22to be certain, rather than relying on the already-published build (which had linked against our now-deleted llvm22) continuing to resolve correctly by luck.
If LLVM-version-pinning ever comes up again for another package
Check pacman -Si llvm<N> / pacman -Ss llvm<N> against the official repos
first, not just AUR. extra has at least llvm22 (confirmed); there may be
others.