pacaur

Synchronize and update all packages (includes AUR)

$ pacaur -Syu

$ pacaur -Syua

$ pacaur -S [package]

$ pacaur -Rs [package]

$ pacaur -Ss [keyword]

$ pacaur -Qs

pacaur [options] [targets]
pacaur {-S | --sync} [options] [packages]
pacaur {-R | --remove} [options] [packages]
pacaur {-Q | --query} [options] [packages]
pacaur {-G | --getpkgbuild} [options] [packages]

-S, --sync
    Synchronize packages, installing or upgrading them. Often combined with -u and -y for system updates.

-R, --remove
    Remove specified packages from the system, potentially with their dependencies.

-Q, --query
    Query the package database for information about installed packages or files.

-u, --sysupgrade
    Upgrade all installed packages that are out-of-date. Typically used with -S and -y.

-y, --refresh
    Download fresh package databases from the server. Always recommended before an upgrade.

-a, --aur
    Include results from the Arch User Repository in searches (e.g., pacaur -SsA).

-i, --info
    Show package information before performing an action (e.g., install).

-G, --getpkgbuild
    Download the PKGBUILD file for a specified package from the AUR without installing it.

--noedit
    Do not open PKGBUILD files for editing before building.

--noconfirm
    Bypass all confirmation prompts. Use with extreme caution as it can lead to unintended installations or removals.

--clean
    Remove old downloaded packages and build directories from the cache to free up disk space.

pacaur was a popular command-line AUR helper for Arch Linux, designed to simplify the process of installing and managing packages from the Arch User Repository (AUR). It acted as a wrapper around pacman and the makepkg utility, automating the steps required to download PKGBUILDs, resolve dependencies, build packages, and install them.

Its interface was largely inspired by pacman, making it intuitive for users familiar with the official package manager. pacaur aimed to provide a secure and reliable way to interact with the AUR, offering features like PGP signature checking and an interactive review of PKGBUILDs before building. While widely adopted for its efficiency and ease of use, pacaur's development ceased, primarily due to the deprecation of its dependency cower and a shift in AUR helper development towards tools like yay and paru. It is now considered unmaintained and should not be used for new installations.

pacaur is deprecated and unmaintained. Its upstream dependency, cower, is also no longer maintained. Using pacaur is strongly discouraged as it may lead to security vulnerabilities, broken builds due to outdated code, or incompatibility issues with recent Arch Linux changes. Users should migrate to actively maintained AUR helpers such as yay or paru for safe and reliable AUR package management.

pacaur was designed with security in mind, offering users the ability to review the PKGBUILD file before building a package. This crucial feature allowed users to inspect the build instructions, source URLs, and installation steps for any malicious code or unintended actions, fostering a more secure interaction with the community-maintained AUR.

pacaur emerged as a popular AUR helper for Arch Linux users seeking a streamlined way to manage packages from the Arch User Repository. It gained significant traction due to its robust feature set, pacman-like interface, and emphasis on security through PKGBUILD review and PGP signature verification. For a period, it was one of the most recommended AUR helpers in the Arch Linux community.

However, its development largely ceased around 2018-2019, primarily driven by the deprecation of its key dependency, cower, and the rise of newer, more actively developed AUR helpers like yay and paru written in Go and Rust respectively. The community gradually shifted away from pacaur due to concerns about unmaintained code and potential future compatibility or security issues. It is no longer advisable to use pacaur for managing AUR packages.

pacman(8), makepkg(8), yay(8), paru(8), cower(1)