|author||Joey Hess <firstname.lastname@example.org>||2011-08-06 18:58:55 -0400|
|committer||Joey Hess <email@example.com>||2011-08-06 18:59:43 -0400|
dpkg-buildflags is only used to set environment in v9
To avoid re-breaking packages that were already broken a first time by dpkg-buildpackage unconditionally setting the environment, and unbroke it by unsetting variables in the rules file. (Example: numpy)
Diffstat (limited to 'debhelper.pod')
1 files changed, 6 insertions, 4 deletions
diff --git a/debhelper.pod b/debhelper.pod
index 9000d69..34a16a3 100644
@@ -191,10 +191,6 @@ in ALL packages acted on, not just the first.
=head1 BUILD SYSTEM OPTIONS
-All of the B<dh_auto_>I<*> debhelper programs set environment variables
-listed by B<dpkg-buildflags>, unless they are already set. They
-support DEB_BUILD_OPTIONS=noopt too.
The following command line options are supported by all of the B<dh_auto_>I<*>
debhelper programs. These programs support a variety of build systems,
and normally heuristically determine which to use, and how to use them.
@@ -489,6 +485,12 @@ in --libexecdir when using autoconf.
B<dh> does not default to enabling --with=python-support
+All of the B<dh_auto_>I<*> debhelper programs and B<dh> set
+environment variables listed by B<dpkg-buildflags>, unless
+they are already set. They support DEB_BUILD_OPTIONS=noopt too.