vp-build/common/hooks
Jürgen Buchmüller d8eca52226 00-distfiles.sh: add code to purge wrong checksum
If a distfile changed its checksum (SHA256) without at the same time
also changing its version, the distfile cache needs to be purged.

This is done by verifying only for already existing distfiles that the
specified checksum matches. If it does not, the file and its entry in
/host/sourcers/by_sha256 are purged using the inode number of the file.

The second loop then as usual fetches the distfiles and verifies their
checksum against the list entry.

+ drbd-utils fix checksum and also build + cross build
2015-11-03 19:27:07 +01:00
..
do-build
do-configure
do-extract xbps-src: distfiles: allow uncompressed distfiles 2015-10-23 20:09:31 +02:00
do-fetch 00-distfiles.sh: add code to purge wrong checksum 2015-11-03 19:27:07 +01:00
do-install
do-pkg xbps-src: support "alternatives" from xbps-0.48. 2015-10-30 12:39:59 +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 xbps-src: replace basename(1) with ${var##*/}. 2015-09-11 07:55:40 +02:00
post-pkg
pre-build
pre-configure wrappers: rename cc to cross-cc to clarify it's used only in cross mode. 2015-10-25 11:03:16 +01:00
pre-extract
pre-fetch
pre-install
pre-pkg pre-pkg/06-shlib-provides.sh: revamp soname registration. 2015-10-06 20:17:28 +02:00
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.