snailed
/
void-packages
2
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Activity
void-packages/common/environment
History
Juan RP 00b8dd7e50 common/env/install: drop timestamp-macros.sh. 
Why? because adding this to the install phase will change the compiler
flags that were used for configure/building and compilation will
happen twice.
 		2016-03-03 07:44:06 +01:00
..
build environment/build: overwrite __DATE__, __TIME__, and __TIMESTAMP__ macros. 2016-03-01 15:33:09 +01:00
build-style go, build-style/go: set nopie=yes 2015-11-19 09:55:48 +01:00
configure common: fix glibc 2016-03-01 20:52:44 +01: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/env/install: drop timestamp-macros.sh. 2016-03-03 07:44:06 +01:00
pkg common: remove unneccessary 'source's; move extglob.sh to install 2015-11-18 10:21:33 +01:00
setup common/environment: only load git commit date when in chroot. 2016-03-02 07:47:35 +01:00
setup-subpkg xbps-src: support "alternatives" from xbps-0.48. 2015-10-30 12:39:59 +01:00
README common/environment/README: build_style -> build-style. 2015-02-21 12:25:57 +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:

	* build-style	(to set vars for a specific build_style helper)
	* 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.