void-packages/common/hooks
newbluemoon e8842e10d7 wxWidgets: fix cross compilation
xbps-src: add wx-config to 02-script-wrapper.sh
2017-12-16 01:48:46 +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: handle .7z distfiles via 7z. 2016-01-11 11:02:44 +01:00
do-fetch 00-distfiles.sh: avoid unnecessary second loop 2015-11-05 22:05:25 +01:00
do-install
do-pkg common: expand_destdir rewrite 2015-11-18 11:19:09 +01:00
post-build
post-check add hook-directories for check phase 2017-11-18 14:32:37 +01:00
post-configure
post-extract hooks/post-extract/00-patches.sh: ignore files without patch/diff suffix 2017-09-26 11:02:37 +00:00
post-fetch
post-install wine: nopie_files 2017-11-29 19:28:02 +01:00
post-pkg hooks/register-pkg: register 32bit pkgs in cross mode too. 2015-02-08 18:13:24 +01:00
pre-build
pre-check add hook-directories for check phase 2017-11-18 14:32:37 +01:00
pre-configure wxWidgets: fix cross compilation 2017-12-16 01:48:46 +01:00
pre-extract
pre-fetch
pre-install xbps-src: fix hooks that are expected to be used in subpkgs. 2015-01-14 14:23:10 +01:00
pre-pkg 03-rewrite-python-shebang.sh: don't rewrite versioned python scripts (#6155) 2017-04-17 08:49:06 +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.