void-packages

History

Alessio Sergi 4e6576e7a4 xbps-src: add support for python3 pkgs - python_module build style now builds modules for python2/3 by default - new python2_module and python3_module build styles for building python2-only and python3-only packages respectively - no more python_versions - no need to define pycompile_version for Python modules anymore (still needed for non-Python modules though) - Python version and paths are now guessed automatically and a set of useful variables can now be used in templates - #!/usr/bin/python2 and #!/usr/bin/python3 are now the default shebangs - /usr/bin/foo2 and /usr/bin/foo3 are now the default names for bin scripts (for use with alternatives)		2016-10-16 16:59:31 +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
post-fetch
post-install	xbps-src: add support for python3 pkgs	2016-10-16 16:59:31 +02:00
post-pkg
pre-build
pre-configure	compiler wrapper: add ccache or distcc prefix (#4575 )	2016-08-08 08:37:06 +02:00
pre-extract
pre-fetch
pre-install
pre-pkg	xbps-src: add support for python3 pkgs	2016-10-16 16:59:31 +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.