teldra
/
vp-build
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
vp-build/common/environment
History
Juan RP c49e01fc15 xbps-src: make it possible to override the subpackages list via ${subpackages}. 
This overrides the automatic list generated by xbps-src and it's overridable
to change the processing order of subpackages.
 		2014-07-23 15:44:36 +02:00
..
build common/environment: create dummy files for all dirs to not remove them. 2014-02-11 18:22:46 +01:00
configure environment/gnu-configure-args: only set --libdir if build_style unset or gnu-configure. 2014-06-11 09:24:44 +02:00
extract common/environment: create dummy files to add required dirs. 2014-02-11 11:29:30 +01:00
fetch common/environment: create dummy files for all dirs to not remove them. 2014-02-11 18:22:46 +01:00
install common/environment: create dummy files for all dirs to not remove them. 2014-02-11 18:22:46 +01:00
pkg common/environment: create dummy files to add required dirs. 2014-02-11 11:29:30 +01:00
setup xbps-src: make it possible to override the subpackages list via ${subpackages}. 2014-07-23 15:44:36 +02:00
setup-subpkg xbps-src: added "pycompile_version" to specify python version used in the pycompile trigger. 2014-06-18 11:31:32 +02:00
README Infrastructure changes to allow unsetting template vars/funcs. 2014-03-19 09:03:21 +01:00

README 

ENVIRONMENT SHELL SNIPPETS
==========================

This directory contains shell files (must not be executable nor contain a shebang)
that are read by xbps-src when building source packages. The shell files
are read in lexical order (as ordered by shell rules).

These files shall set or unset environment variables while building packages.
Only files with the `.sh' extension are read, so this file will be simply ignored.

The following directories are used to set the order in which the shell snippets
should be read by xbps-src:

	* setup		(before reading template)
	* setup-subpkg	(before running the subpkg <pkgname>_package() function)
	* fetch		(before running fetch phase)
	* extract	(before running extract phase)
	* configure	(before running configure phase)
	* build		(before running build phase)
	* install	(before running install phase)
	* pkg		(before running pkg phase)

NOTES
~~~~~
* Symlinks can be created (relative) to make a shell snippet available in
  multiple phases.