From 2d8a751943abfe6c32fdc6957d61848d5eb0e4ca Mon Sep 17 00:00:00 2001
From: Jouke Witteveen <j.witteveen@gmail.com>
Date: Wed, 25 Jul 2018 18:53:03 +0200
Subject: alpm-hooks.5: include more information on hook files

Signed-off-by: Allan McRae <allan@archlinux.org>
---
 doc/alpm-hooks.5.asciidoc | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

(limited to 'doc/alpm-hooks.5.asciidoc')

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
 --------
-- 
cgit v1.2.3-70-g09d2

