void-packages

History

q66 ec937e4d29 environment/build-style/go.sh: specify a default set of archs This is necessary so that crossbuilds to unsupported architectures are not actually attempted. There is a default archs set which covers all architectures supported by the official compiler, and setting it in the template can be used to restrict it more. Also, add missing GOARCHs. These are irrelevant to whether we can currently build for that arch or not. Just keep it around as a list of potential archs to support. These are taken from gccgo, and in case support for anything is added in the official compiler, they should match.		2020-03-30 05:32:09 +02:00
..
build
build-style	environment/build-style/go.sh: specify a default set of archs	2020-03-30 05:32:09 +02:00
check
configure	git: update to 2.25.2.	2020-03-18 09:34:32 +01:00
extract
fetch	environment/fetch: add cmd_fetch variable.	2019-01-21 16:17:02 -02:00
install
patch	meta: link .sh from configure into patch envrionment.	2019-03-03 13:08:23 -03:00
pkg
setup	common/environment/setup/python.sh: update to Python 3.8.	2019-12-23 14:11:45 +01:00
setup-subpkg	meta: remove supporting code for noarch	2019-03-14 19:22:06 -03:00
README

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)
	* check		(before running check 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.