aurutils

aur-build [options] pkgbase...
aur-check [options] pkgbase...
aur-chroot [options] command...
aur-repo [options] subcommand...
aur-sync [options] [pkgbase...]

aur-build
    Builds AUR packages within a chroot environment, producing a `.pkg.tar.zst` file.

aur-check
    Checks for updates to installed AUR packages and their dependencies.

aur-chroot
    Manages and interacts with chroot build environments.

aur-repo
    Manages local Arch Linux package repositories, adding or removing built packages.

aur-sync
    Synchronizes the local repository with AUR packages, pulling updates and initiating builds.

aurutils is a collection of tools designed to manage Arch User Repository (AUR) packages in a secure and pacman-centric way. Unlike many other AUR helpers, aurutils doesn't directly install packages after building them. Instead, it facilitates the creation and management of local Arch Linux package repositories. This approach treats AUR packages much like official ones: they are built, signed, and then added to a local repository, from which they can be installed and updated using standard pacman commands.

Key features include:

• Chroot builds: Packages are built in isolated chroot environments to enhance security and prevent build-time conflicts with the host system.
• Local repository management: Tools to create, update, and manage your own package repositories, integrating seamlessly with pacman.
• Dependency handling: Automatically resolves and includes AUR dependencies, allowing for a complete build process.
• Update checking: Efficiently checks for updates to both explicitly installed AUR packages and their dependencies.
• Package signing: Supports GPG signing of built packages for added integrity verification.

aurutils appeals to users who prefer a robust, transparent, and highly integrated workflow for managing AUR software, treating AUR as a natural extension of the official repositories via local caches.

aurutils offers a powerful and secure workflow, but comes with a steeper learning curve compared to simpler AUR helpers. Users need a good understanding of pacman, makepkg, and the concept of local repositories. Its configuration, primarily through aur.conf, requires manual setup for repositories and build environments. While chroot builds enhance security, users are still responsible for reviewing PKGBUILD files to understand what scripts will be run and what sources will be fetched. Misconfiguration can lead to unexpected behavior or repository issues.

aurutils relies heavily on its configuration file, typically located at `/etc/aurutils/aur.conf` or `~/.config/aurutils/aur.conf`. This file defines the paths to your local repositories, build directories, and specifies chroot environments. Proper setup of this file is crucial for aurutils to function correctly.

A common workflow involves adding desired AUR packages to your aur.conf, then running aur-sync to fetch and build them. Once built and added to your local repository by `aur-repo`, packages can be installed and managed like any other official package using `sudo pacman -S package_name`, after ensuring your local repository is configured in `/etc/pacman.conf`.

Developed by Alad (Alexander F. Rødseth), aurutils emerged as a response to the need for a more robust and secure method of managing AUR packages. Its development focused on leveraging existing Arch Linux tools like pacman and makepkg, rather than reinventing package management. The philosophy behind aurutils was to integrate AUR packages into the system in a way that closely mirrors official packages, particularly through the use of local repositories and mandatory chroot builds. This approach quickly resonated with experienced Arch Linux users seeking a more controlled and transparent AUR workflow, solidifying its place as a trusted helper for advanced users.

pacman(8), makepkg(8), repo-add(8), git(1), systemd-nspawn(1), arch-chroot(8)