[pacman-dev] [PATCH v2] alpm-hooks.5: include more information on hook files

Jouke Witteveen j.witteveen at gmail.com
Fri Jun 22 16:16:22 UTC 2018


---
I'm sorry for sending a revision of such a minor patch, but I could not stand
having messed up the line lengths.

This is a follow-up to my hook sorting patch.

The information added is also available in pacman.conf(5), and in pacman(8), but
this looks like a good place to repeat it.

Regards,
- Jouke

 doc/alpm-hooks.5.asciidoc | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/doc/alpm-hooks.5.asciidoc b/doc/alpm-hooks.5.asciidoc
index 1d19f96e..e6f1f8e3 100644
--- a/doc/alpm-hooks.5.asciidoc
+++ b/doc/alpm-hooks.5.asciidoc
@@ -30,9 +30,14 @@ 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
-file names are required to have the suffix ".hook".  Hooks are run in
-alphabetical order of their file name.
+'[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.  Additional
+directories are specified linkman:pacman.conf[5].  The default additional
+directory is +{sysconfdir}/pacman.d/hooks+.  Hook file names are required to
+have the suffix ".hook".  Hooks are run in alphabetical order of their file
+name, where the ordering ignores the suffix.
 
 TRIGGERS
 --------
-- 
2.18.0


More information about the pacman-dev mailing list