void-packages/common/hooks
Đoàn Trần Công Danh 90860e279e do-fetch: remove support for rpm contents checksum
It doesn't make sense to support contents checksum here.
2023-01-25 07:43:44 +07:00
..
do-build
do-check
do-configure
do-extract do-extract: extract rpm with bsdtar, too 2022-11-30 23:20:04 +07:00
do-fetch do-fetch: remove support for rpm contents checksum 2023-01-25 07:43:44 +07:00
do-install
do-patch common/do-patch: handle spaces in patch filename 2022-05-19 20:56:42 +02:00
do-pkg xbps-src: overwrite packages in local repo 2021-09-13 23:04:48 +02:00
post-build
post-check
post-configure
post-extract
post-fetch
post-install 11-pkglint-elf-in-usrshare: use file --no-pad so we don't have to strip it 2022-09-03 15:30:51 +02:00
post-patch
post-pkg
pre-build
pre-check
pre-configure python3: update to 3.11.0. 2022-11-05 08:21:20 -04:00
pre-extract
pre-fetch
pre-install
pre-patch
pre-pkg gen-runtime-deps: verify rdeps for shlib_requires too 2022-11-30 23:22:16 +07:00
README

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.