void-packages/common/hooks
Juan RP 9df1aa3b4e hooks/post-install/create-xbps-metadata-scripts: make sure to finalize scripts correctly.
The issue was that if a pkg does not add the missing newline at INSTALL
or REMOVE scripts, those were generated with a syntax error.

Found by onekk.
2014-04-14 10:41:06 +02:00
..
do-build common/hooks: add support for do-<phase> hooks as suggested by Gottox. 2014-03-05 11:02:37 +01:00
do-configure common/hooks: add support for do-<phase> hooks as suggested by Gottox. 2014-03-05 11:02:37 +01:00
do-extract hooks/do-extract/distfiles: simplify and support .tar.lz files. 2014-03-14 11:04:51 +01:00
do-fetch hooks/do-fetch/distfiles: do not strip '>*' in url, pass it as is. 2014-03-12 15:47:49 +01:00
do-install common/hooks: add support for do-<phase> hooks as suggested by Gottox. 2014-03-05 11:02:37 +01:00
do-pkg hooks/do-pkg/gen-pkg: do not propagate conf_files/provides/replaces to 32bit pkgs. 2014-03-09 08:59:22 +01:00
post-build Introduce common/hooks to implement hooks at specified phases. 2014-02-12 10:44:21 +01:00
post-configure Introduce common/hooks to implement hooks at specified phases. 2014-02-12 10:44:21 +01:00
post-extract common/hooks: add support for do-<phase> hooks as suggested by Gottox. 2014-03-05 11:02:37 +01:00
post-fetch Introduce common/hooks to implement hooks at specified phases. 2014-02-12 10:44:21 +01:00
post-install hooks/post-install/create-xbps-metadata-scripts: make sure to finalize scripts correctly. 2014-04-14 10:41:06 +02:00
post-pkg hooks: only generate/register 32bit pkgs on x86. 2014-03-07 10:12:20 +01:00
pre-build Introduce common/hooks to implement hooks at specified phases. 2014-02-12 10:44:21 +01:00
pre-configure common/hooks: add support for do-<phase> hooks as suggested by Gottox. 2014-03-05 11:02:37 +01:00
pre-extract Introduce common/hooks to implement hooks at specified phases. 2014-02-12 10:44:21 +01:00
pre-fetch Introduce common/hooks to implement hooks at specified phases. 2014-02-12 10:44:21 +01:00
pre-install Use --libdir=/usr/lib32 on x86 and create/remove the symlink via hooks. 2014-04-05 11:52:22 +02:00
pre-pkg common/hooks: add support for do-<phase> hooks as suggested by Gottox. 2014-03-05 11:02:37 +01:00
README common/hooks: add support for do-<phase> hooks as suggested by Gottox. 2014-03-05 11:02:37 +01:00

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.