[pacman-dev] [PATCH v3 10/11] add alpm-hooks man page

Allan McRae allan at archlinux.org
Sun Oct 18 00:11:39 UTC 2015

On 17/10/15 10:28, Andrew Gregory wrote:
> Signed-off-by: Andrew Gregory <andrew.gregory.8 at gmail.com>
> ---

Two things.   I think this should be named "libalpm-hooks".

> +-------
> +
> +There is no way to guarantee that the trigger operation was actually performed
> +for file triggers.  Removal triggers will match even if the file did not
> +actually exist on the file system when the transaction begin.  Installed or
> +upgraded files may be extracted with a '.pacnew' extension, leaving the path in
> +the trigger unmodified.

This still confuses me - it sound like documentation written by the
person who wrote the feature!  How about:

There are situations when file triggers may act in unexpected ways.
Hooks are triggered using the file list of the installed, upgraded, or
removed package.  When installing or upgrading a file that is extracted
with a '.pacnew' extension, the original file name is used in triggering
the hook.  When removing a package, all files owned by that package can
trigger a hook whether or not they were actually present on the file
system before package removal.

More information about the pacman-dev mailing list