index : pacman | |
Archlinux32 fork of pacman | gitolite user |
summaryrefslogtreecommitdiff |
author | Jouke Witteveen <j.witteveen@gmail.com> | 2018-07-25 18:53:03 +0200 |
---|---|---|
committer | Allan McRae <allan@archlinux.org> | 2018-07-27 11:04:02 +1000 |
commit | 2d8a751943abfe6c32fdc6957d61848d5eb0e4ca (patch) | |
tree | 72bf55e7ddb491f10c7a6e7bada523d47d52a924 /doc/alpm-hooks.5.asciidoc | |
parent | 13fb2430e8e2c5f266e43da85d9adbe5284f0080 (diff) |
-rw-r--r-- | doc/alpm-hooks.5.asciidoc | 8 |
diff --git a/doc/alpm-hooks.5.asciidoc b/doc/alpm-hooks.5.asciidoc index 1d19f96e..0f6a1057 100644 --- a/doc/alpm-hooks.5.asciidoc +++ b/doc/alpm-hooks.5.asciidoc @@ -30,9 +30,13 @@ DESCRIPTION libalpm provides the ability to specify hooks to run before or after transactions based on the packages and/or files being modified. Hooks consist of a single '[Action]' section describing the action to be run and one or more -'[Trigger]' section describing which transactions it should be run for. Hook +'[Trigger]' section describing which transactions it should be run for. + +Hooks are read from files located in the system hook directory ++{datarootdir}/libalpm/hooks+, and additional custom directories specified in +linkman:pacman.conf[5] (the default is +{sysconfdir}/pacman.d/hooks+). The file names are required to have the suffix ".hook". Hooks are run in -alphabetical order of their file name. +alphabetical order of their file name, where the ordering ignores the suffix. TRIGGERS -------- |