vp-build/common/hooks
Enno Boland 66cdb281f1 hooks/pre-configure: don't overwrite PKG_CONFIG_* vars in the wrapper.
This may have side effects do other packages but it was needed to fix
gnome-online-accounts for cross build. goa ships a subproject that uses
this vars to link against it. This commit changes the pkg-config that it
preserves values in PKG_CONFIG_* if set.
2015-10-13 15:01:32 +02:00
..
do-build
do-configure
do-extract
do-fetch xbps-src: replace basename(1) with ${var##*/}. 2015-09-11 07:55:40 +02:00
do-install
do-pkg hooks/do-pkg/gen-pkg: don't set unnecessary args to xbps-create(1). 2015-09-10 20:07:13 +02:00
post-build
post-configure
post-extract xbps-src: replace basename(1) with ${var##*/}. 2015-09-11 07:55:40 +02:00
post-fetch
post-install xbps-src: replace basename(1) with ${var##*/}. 2015-09-11 07:55:40 +02:00
post-pkg
pre-build
pre-configure hooks/pre-configure: don't overwrite PKG_CONFIG_* vars in the wrapper. 2015-10-13 15:01:32 +02:00
pre-extract
pre-fetch
pre-install
pre-pkg pre-pkg/06-shlib-provides.sh: revamp soname registration. 2015-10-06 20:17:28 +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.