Tried to document some of the *_ENV variables. There are still many TODO

and XXX tags.

1 files changed, 66 insertions, 0 deletions

diff --git a/mk/help/env.mk b/mk/help/env.mk
new file mode 100644
index 00000000000..1989a68fd80
--- /dev/null
+++ b/mk/help/env.mk
@@ -0,0 +1,66 @@
+# $NetBSD: env.mk,v 1.1 2006/10/25 17:21:35 rillig Exp $
+#
+# This file describes the *_ENV variables, where they are defined and
+# where they are used.
+#
+# In general, all environments should be ordered from general to specific
+# ones. That is, first comes the BARRIER_ENV, then the MAKE_ENV, then the
+# MAKE_BUILD_ENV.
+#
+# Additionally, the package should be able to override all settings from
+# the infrastructure. That means that the package-settable variables
+# must appear behind the system-defined ones.
+#
+
+# XXX: I'm missing BARRIER_ENV or something like that.
+
+# XXX: The do-* targets are not run with ALL_ENV (or better:
+# BARRIER_ENV) in effect.
+
+#
+# Common environments.
+#
+
+# PKGSRC_MAKE_ENV
+#
+
+# ALL_ENV
+#	This is the basic environment for the configure, build and install
+#	phases. It can be overridden by CONFIGURE_ENV and MAKE_ENV.
+#
+
+#
+# Environments for individual phases.
+#
+
+# EXTRACT_ENV
+
+# CONFIGURE_ENV
+
+# MAKE_ENV
+
+# BSD_MAKE_ENV
+#	This environment can be appended to MAKE_ENV by a package to
+#	support packages using BSD-style Makefiles, for example
+#	<bsd.prog.mk>.
+#
+
+# INSTALL_ENV
+#	This environment is prepended to MAKE_ENV in the install phase.
+#	XXX: Shouldn't this be _ap_pended?
+
+#
+# Other environments.
+#
+
+# SCRIPTS_ENV
+#	TODO
+#
+
+# INSTALL_SCRIPTS_ENV
+#	TODO
+#
+
+# PKGTOOLS_ENV
+#	TODO
+#