This page is locked. All discussion to the pacman-dev mailing list. The discussion page will be ignored...
We will one day live in a world where we no longer have to suffer the tedium of repeated tasks in pacman install files. The future will arrive bearing the stuff of legends... Things that have been talked about in quiet whispers for decades. Pacman hooks!
Hook files are placed in /usr/lib/pacman/hooks or /etc/pacman.d/hooks. Those in /etc override those in /usr/lib. An empty file in /etc disables the hook in /usr/lib.
Hook files require the .hook suffix.
[Hook] Description = Add info files to the info directory Requires = install-info Type = PostTransaction [Target] File = /usr/share/info/* Exec = install-info %f usr/share/info/dir &>/dev/null
Description: (Optional) Brief description of the hook
Requires: (Optional) Required software for hook to run
- Before the installation/upgrade of the package (PreInstall)
- After the installation/upgrade of the package (PostInstall)
- Before the removal of the package (PreRemove)
- After the removal of the package (PostRemove)
- At the beginning of the transaction (PreTransaction)
- At the end of the transaction (PostTransaction)
Before/After: (Optional) Control the ordering of the hook
File: File or list of files that trigger a hook.
Package: Package or list of packages that trigger the hook.
Exec: the command to be run during the upgrade. Can use the following replacements (will be quoted):
%f: the triggering file - if more than one triggers, the command is looped %F: the list of triggering files %p: the triggering package - if more than one triggers, the command is looped %P: the list of triggering packages
During ./configure the system hooks directory is specified with --with-hooksdir defaulting to EPREFIX/lib when unspecified. The override directory is not configurable beyond using --sysconfdir.
- Should non-transaction File hooks be run after the file is installed or at the end of each package
- How do we handing installation of new hooks during transaction.