aur
Install, manage, and search AUR packages
TLDR
Initialize the repository that matches the path in /etc/pacman.conf
Search the AUR database for a package
Download one or more packages and their dependencies from the AUR, build them, and add them to a local repository
List packages available in your local repository
Upgrade local repository packages
Clean build files after install
Install a package without viewing changes in Vim and do not confirm dependency installation
Remove a package form the repository metadata (does not remove the package file itself)
SYNOPSIS
aur [-S|--sync] [-Q|--query] [-R|--remove] [-Sw|--sync dep] [options] [pkg...]
PARAMETERS
-S, --sync
Install/sync packages from AUR (builds PKGBUILDs)
-Syu, --sync --sysupgrade
Full system upgrade (official + AUR repos)
-Qs, --query search
Search AUR packages by name/description
-Si, --info
Show detailed info for AUR package
-Sw, --sync --needed --no-upgrade
Download PKGBUILDs without building
-R, --remove
Remove installed AUR packages
--aur
Limit operations to AUR (some helpers)
-c, --clean
Clean build dependencies after install
--bottom-up
Build dependencies bottom-up (avoids partial fails)
-m, --mflags
Pass makepkg flags (e.g., -m "--skippgpcheck")
DESCRIPTION
The aur command typically refers to unofficial helper tools for the Arch User Repository (AUR) on Arch Linux and derivatives. AUR is a community-driven collection of PKGBUILD recipes for building packages from source, extending beyond official repos.
No official aur binary exists in Arch Linux; users rely on third-party AUR helpers mimicking pacman syntax. These tools handle searching AUR, downloading PKGBUILDs via git, resolving dependencies (including splitting binary/AUR deps), building with makepkg, and installing. Popular helpers include yay (Go-based, full-featured), paru (Rust, AUR-focused), and aurutils (bash scripts, lightweight).
Helpers streamline workflows but require caution: AUR packages are unvetted, potentially malicious. Always review PKGBUILDs and sources before building. Common use cases: installing niche software unavailable in official repos, like custom kernels or bleeding-edge apps.
Syntax varies slightly by helper, but most emulate pacman for familiarity.
CAVEATS
No official aur command exists; syntax varies by helper (e.g., yay, paru). AUR packages are user-maintained: review PKGBUILDs to avoid malware. Helpers may cache sources insecurely or automate blindly. Building requires base-devel group. Not suitable for servers (build isolation issues).
POPULAR HELPERS
yay: pacman-compatible, Go-lang. Install: git clone https://aur.archlinux.org/yay.git; makepkg -si.
paru: Rust, edit-build menu. Similar install.
helaur: Haskell, lightweight.
MANUAL WORKFLOW
git clone https://aur.archlinux.org/<pkg>.git
cd <pkg>
makepkg -si
Review PKGBUILD first!
AUR WEBSITE
Search/browse at aur.archlinux.org. Use asp (Arch Submission Program) for exports: asp export pkgname.
HISTORY
AUR created in 2007 by Tom Kraynok for community PKGBUILDs. Early helpers: yaourt, packer (2010s, now deprecated due to issues). Modern era: yay (2018, by Jguer), paru (2019, by Morganamilo), pikaur. aurutils (2017+) emphasizes manual control. Helpers evolved to handle dependency resolution post-cower deprecation.


