FS#48696 - [pacman] [PATCH] pacman.conf.5: clarify that /etc/pacman.d/hooks/ is assigned by default

Attached to Project: Pacman
Opened by Dario Giovannetti (kynikos) - Saturday, 26 March 2016, 02:58 GMT
Last edited by Allan McRae (Allan) - Tuesday, 29 March 2016, 04:21 GMT
Task Type Bug Report
Category Documentation
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version 5.0.1
Due in Version 5.1.0
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

As discovered in [1], pacman.conf(5) seems to say that /etc/pacman.d/hooks/ is only a suggested ("typical") value for HookDir, while that path is indeed assigned if the option is not defined in pacman.conf.[2]

[1] https://wiki.archlinux.org/index.php/User_talk:Kale-ru#Pacman_hooks
[2] https://projects.archlinux.org/pacman.git/tree/src/pacman/conf.c#n759

This patch tries to clarify that, as has already been done on the wiki.[3]

[3] https://wiki.archlinux.org/index.php?title=Pacman&diff=next&oldid=427412
   0001-pacman.conf.5-clarify-et... (1 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 29 March 2016, 04:21 GMT
Reason for closing:  Fixed
Additional comments about closing:  git commit 4960be77
Comment by Alastair Hughes (pypi) - Saturday, 26 March 2016, 04:17 GMT
The same wording is used in the man page for pacman, for other options as well - searching for 'typical default' brings up a few hits. The 'typical default' wording was around when the paths where hard coded in the docs, which made sense then. I note that just 'default' is used in makepkg's man pages, so perhaps just using that might make more sense?
I've attached a patch changing all occurrences of 'a typical default' to 'the default'.

The change from explicit to config-dependent paths was in 05f0a289, see [1].

[1] https://lists.archlinux.org/pipermail/pacman-dev/2010-October/011792.html
   0001-Changed-documentation-to... (4.7 KiB)

Loading...