Automating System Maintenance with Pacman Hooks
Stop manually restarting services and rebuilding configs after updates. Learn how to use Arch Linux pacman hooks to automate your system maintenance declaratively.
Loading…
ReadMeFeed / Community knowledge
#pacman
Real questions. Useful conversations. Find the people who know your stack.
archlinuxCreating a Pacman Hook to Run a Script After Package Upgrades in Arch Linux
Step‑by‑step guide to create a Pacman hook that runs a custom script after every package upgrade or install in Arch Linux.
Understanding Artix Linux’s artix-archlinux-support Repository: Design and Safe Usage
A concise guide to Artix Linux’s artix-archlinux-support repository: its design, trust boundaries, operational checks, failure modes, and safe usage steps.
artixlinuxManaging Arch Linux Dependencies: Avoiding Partial Upgrades
Learn why partial upgrades break Arch Linux systems and how to master pacman's dependency resolution mechanism to maintain a stable rolling release.
Automating Kernel Updates on Arch Linux with Pacman Hooks
Learn how to use a Pacman hook to automatically detect kernel upgrades on Arch Linux and optionally reboot, reducing manual update overhead.
ParallelDownloads in pacman 6.0: Picking a Per-Mirror Concurrency Limit
pacman 6.0 introduced the ParallelDownloads option in /etc/pacman.conf , replacing the earlier strictly sequential fetch behavior within a single transaction. The option accepts a positive integer, and because Arch is a rolling release, the installed pacman version governs how that value is parsed and what happens when the line remains commented out. Upgrade
Pacman ParallelDownloads and systemd-journald interaction under concurrent package installations
Goal Reduce the observable latency that occurs when multiple pacman package installation requests run concurrently, while preserving the integrity of the package database. Constraints and uncertainty Pacman serializes write access via a database lock file; the ParallelDownloads option only parallelizes the download phase, so concurrent processes still block
Unsupported partial upgrade state in pacman dependency resolution
Arch Linux utilizes a rolling release model where pacman manages dependencies through a directed graph to ensure library compatibility. The system documentation explicitly states that partial upgrades—synchronizing the package database without performing a full system upgrade—are unsupported. When a user executes pacman -Sy followed by the installation of a
Pacman automatic orphaned package removal configuration
The goal is to lower the operating cost of a low‑traffic Arch Linux host by ensuring that packages which become orphaned after a dependent application is removed are automatically eliminated, thereby freeing disk space and reducing the attack surface. Pacman maintains a dependency graph and can list orphaned packages, but it does not perform removal without