void-packages

History

tibequadorian 15f5a8668b patch_args: allow use of --directory parameter patch(1) has a -d/--directory parameter which allows us to specify a directory where the patch will be applied. This is especially useful when we have multiple distfiles and want to patch in $build_wrksrc because that's where the patch is usually applied. Problem is, that the -i parameter is also relative to the the -d parameter and thus fails to find the patch, when -d is set. We solve that by using standard input instead of -i.		2022-04-10 11:06:32 +02:00
..
do-build
do-check
do-configure
do-extract	xbps-src: quote wrksrc to allow whitespace	2020-09-03 21:03:32 +02:00
do-fetch	00-distfiles.sh: fix status phrasing	2020-05-10 10:57:40 +02:00
do-install
do-patch	patch_args: allow use of --directory parameter	2022-04-10 11:06:32 +02:00
do-pkg	xbps-src: overwrite packages in local repo	2021-09-13 23:04:48 +02:00
post-build
post-check
post-configure
post-extract
post-fetch
post-install	nostrip_files: allow full path	2022-01-08 17:51:54 +01:00
post-patch
post-pkg	common/hooks: simplify setting arch for binpkg	2021-09-13 23:04:48 +02:00
pre-build
pre-check
pre-configure	python3: update to 3.10.0.	2021-10-09 08:00:19 -04:00
pre-extract
pre-fetch
pre-install	common/00-libdir: only create lib{32,64} symlink if not exists	2021-02-10 14:38:59 +01:00
pre-patch
pre-pkg	common: fix tooling section in comments	2021-10-24 21:33:13 +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.