void-packages

History

Juan RP d2bac19750 xbps-src: re-introduce etc/virtual. The `etc/virtual` file declares the default package to be built for virtual dependencies declared as "virtual?foo" in $depends. Before this change, the run-time dependency was added as is to the final binary package but no pkg providing this virtual pkg was built. With this file we declare the default pkg to be built. NOTE: "virtual?foo" is only applicable to run time dependencies, i.e only those declared in $depends.		2016-04-27 20:16:59 +02:00
..
do-build
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-configure
post-extract	xbps-src: replace basename(1) with ${var##*/}.	2015-09-11 07:55:40 +02:00
post-fetch
post-install	common/hooks: fix python shebang rewrite for multi-versioned packages	2016-03-27 12:25:27 +02:00
post-pkg
pre-build
pre-configure	gcc: add support for SOURCE_DATE_EPOCH environment	2016-03-08 13:49:52 +01:00
pre-extract
pre-fetch
pre-install
pre-pkg	xbps-src: re-introduce etc/virtual.	2016-04-27 20:16:59 +02: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.