Package sources for all the Arch User Repository (AUR) packages I maintain or co-maintain.
I try my best to follow the packaging guidelines as documented by:
- https://wiki.archlinux.org/title/Arch_package_guidelines
- https://wiki.archlinux.org/title/Arch_package_guidelines/Security
- https://wiki.archlinux.org/title/creating_packages
Additionally, my goal is take advantage of tooling as much as possible. My main
work horse is a custom aurutils command, aur-commit
from
carlsmedstad/aurutils-extra, which performs a number of checks in addition
to building packages.
All packages, except those in .nvcheckerignore
, contain a
.nvchecker.toml
file and new version can as such be discovered using
nvchecker. To check for new versions, run:
make check-versions
NOTE: This functionality relies on an as-of-yet unreleased version of
pkgctl
from devtools
While there are great tools for maintaining super repositories for AUR
packages, for example aurpublish, none of them caught my liking. As such I
wrote my own, aur-sync-super-repo
from carlsmedstad/aurutils-extra with
the following characteristics:
-
Intentionally exclude the ability push changes to packages from within the super repository. I prefer to work in the standalone package repositories and use this repository mostly for sharing my PKGBUILDs.
-
Simple and linear commit history. I don't have the need to be able to track all the changes to individual packages in this repository and prefer to keep the commit history clean.
Updates to this repository are currently done manually (semi-regularly) by executing the following:
make sync
All package additions and edits authored by me are licensed under the Zero-Clause BSD license. To check if a change is authored by me, refer to the corresponding AUR repository.