void-packages/common/hooks
q66 7b4119df5c common/hooks/do-patch/00-patches: drop -l option
The -l option causes a looser behavior of patch(1), where patches
are applied when there is a match with no regard to leading
whitespace. This means that it is possible to get false positives:
for example, in srcpkgs/glu, there is a patch that was supposed
to be long gone (since the release already includes it) but it
was overlooked since with -l it happens to apply in a different
portion of the source (where it is wrong).

Avoid these cases.
2021-11-05 01:44:16 +01:00
..
do-build
do-check add hook-directories for check phase 2017-11-18 14:32:37 +01:00
do-configure
do-extract xbps-src: quote wrksrc to allow whitespace 2020-09-03 21:03:32 +02:00
do-fetch 00-distfiles.sh: fix status phrasing 2020-05-10 10:57:40 +02:00
do-install
do-patch common/hooks/do-patch/00-patches: drop -l option 2021-11-05 01:44:16 +01:00
do-pkg xbps-src: overwrite packages in local repo 2021-09-13 23:04:48 +02:00
post-build
post-check add hook-directories for check phase 2017-11-18 14:32:37 +01:00
post-configure
post-extract meta: move 00-patches.sh hook to do-patch phase 2019-02-27 22:56:19 -03:00
post-fetch
post-install python3: update to 3.10.0. 2021-10-09 08:00:19 -04:00
post-patch meta: add hook directories for patch phase 2019-02-27 22:56:19 -03:00
post-pkg common/hooks: simplify setting arch for binpkg 2021-09-13 23:04:48 +02:00
pre-build
pre-check add hook-directories for check phase 2017-11-18 14:32:37 +01:00
pre-configure python3: update to 3.10.0. 2021-10-09 08:00:19 -04:00
pre-extract
pre-fetch
pre-install common/00-libdir: only create lib{32,64} symlink if not exists 2021-02-10 14:38:59 +01:00
pre-patch meta: add hook directories for patch phase 2019-02-27 22:56:19 -03:00
pre-pkg common: fix tooling section in comments 2021-10-24 21:33:13 +02:00
README

HOOKS
=====

This directory contains shell hooks that are processed after or before the
specified phase. The shell hooks are simply shell snippets (must not be
executable nor contain a shebang) that are processed lexically by xbps-src.
Only files with the `.sh` extension are processed.

A shell hook must provide a `hook()` function which is the entry point to
execute it via xbps-src.

The following directories are used to set the order in which the hooks
should be processed by xbps-src:

	* pre-fetch		(before running fetch phase)
	* do-fetch		(running fetch phase)
	* post-fetch		(after running fetch phase)

	* pre-extract		(before running extract phase)
	* do-extract		(running extract phase)
	* post-extract		(after running extract phase)

	* pre-configure		(before running configure phase)
	* do-configure		(running configure phase)
	* post-configure	(after running configure phase)

	* pre-build		(before running build phase)
	* do-build		(running build phase)
	* post-build		(after running build phase)

	* pre-install		(before running install phase)
	* do-install		(running install phase)
	* post-install		(after running install phase)

	* pre-pkg		(before running pkg phase)
	* do-pkg		(running pkg phase)
	* post-pkg		(after running pkg phase)

NOTES
~~~~~
* Symlinks can be created (relative) to make a hook available in multiple phases.

* The phases do-fetch, do-extract, do-configure, do-build, and do-install can
  be overwritten by the template file. That means if a template contains a
  do_install function, the hooks defined for do-install won't be executed.
  Note that this is only true for the do-* hooks.

* the pre_* function of the template will be run *after* the corresponding
  pre-* hooks.

* the post_* function of the template will be run *before* the corresponding
  post-* hooks.