winpodx-git — AUR development package
Builds winpodx from the GitHub main branch (latest, unreleased code), as a
separate AUR package from the stable winpodx (which uses tagged
release tarballs).
How it stays current
The version is not hand-maintained. pkgver() derives it from git at build
time:
0.6.0.r12.gabc1234 = <last tag> . r<commits since tag> . g<short hash>
So you publish this PKGBUILD to AUR once. Every rebuild re-runs pkgver()
against fresh main, so the version tracks the newest commit automatically.
- Users get updates with
yay -Syu --devel/paru -Syu --devel(the--develpass re-checks VCS packages and rebuilds whenmainmoved). Without--devel, a user reinstalls (yay -S winpodx-git) to pull latest. winpodx-gitandwinpodxcan't coexist (provides/conflicts).- Pin instead of tracking main: add a fragment to
source, e.g.…winpodx.git#commit=<sha>or#tag=v0.6.0. (If you want a fixed version, the stablewinpodxpackage is the better choice.)
Publishing to AUR (maintainer steps)
One-time account + SSH-key setup is identical to the stable package — see
packaging/aur/README.md (generate ~/.ssh/aur_winpodx,
upload the .pub to your AUR profile). The same key works for every package
on your AUR account, so reuse the existing aur_winpodx key.
# Point git at the AUR key (same line the stable winpodx publish uses).
export GIT_SSH_COMMAND="ssh -i ~/.ssh/aur_winpodx -o IdentitiesOnly=yes"
# 1. Clone the (empty) AUR repo — created on first push.
git clone ssh://aur@aur.archlinux.org/winpodx-git.git
cd winpodx-git
# 2. Copy the package files from this repo.
cp /path/to/winpodx/packaging/aur-git/PKGBUILD .
cp /path/to/winpodx/packaging/aur-git/winpodx.install .
# 3. Regenerate .SRCINFO from the PKGBUILD (AUR validates it; the one in this
# repo is a starting point — always regenerate on an Arch box).
makepkg --printsrcinfo > .SRCINFO
# 4. (recommended) Test-build locally first.
makepkg -si
# 5. Commit + push — this publishes / updates the AUR package.
git add PKGBUILD .SRCINFO winpodx.install
git commit -m "winpodx-git: build from main"
git push
Re-push only when the build recipe changes (deps, install steps) — not per
upstream commit; the git source + pkgver() handle commit tracking.