void-packages/common/hooks
classabbyamp afea603940 common/hooks/pre-pkg/04-generate-runtime-deps: support SONAME as path
neovim looks for a SONAME that is a whole path

find: warning: ‘-name’ matches against basenames only, but the given pattern
  contains a directory separator (‘/’), thus the expression will evaluate to
  false all the time.  Did you mean ‘-wholename’?
    SONAME: /usr/lib/lua/5.1/lpeg.so <-> lua51-lpeg>=1.1.0_2
2024-05-21 18:23:18 -04:00
..
do-build
do-check
do-configure
do-extract do-extract: move main logic into helper function 2023-08-21 11:27:32 +07:00
do-fetch xbps-src: abstract away non-portable stat(1) 2023-09-14 08:48:59 +07:00
do-install
do-patch common/do-patch: handle spaces in patch filename 2022-05-19 20:56:42 +02:00
do-pkg
post-build
post-check
post-configure
post-extract
post-fetch
post-install common: support disabling python shebang rewriting 2024-04-23 23:51:01 -04:00
post-patch
post-pkg xbps-src: Replace non-standard English "unexistent" with "nonexistent" 2023-04-17 12:44:48 -05:00
pre-build
pre-check
pre-configure apr: update to 1.7.4. 2024-03-31 06:21:20 +07:00
pre-extract
pre-fetch
pre-install
pre-patch
pre-pkg common/hooks/pre-pkg/04-generate-runtime-deps: support SONAME as path 2024-05-21 18:23:18 -04: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.