From cf88cb54bfc44e8a48eacc3bd6e852d7413780f7 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 6 Aug 2011 18:58:55 -0400 Subject: 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) --- debhelper.pod | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'debhelper.pod') diff --git a/debhelper.pod b/debhelper.pod index 9000d69..34a16a3 100644 --- a/debhelper.pod +++ b/debhelper.pod @@ -191,10 +191,6 @@ in ALL packages acted on, not just the first. =head1 BUILD SYSTEM OPTIONS -All of the BI<*> debhelper programs set environment variables -listed by B, unless they are already set. They -support DEB_BUILD_OPTIONS=noopt too. - The following command line options are supported by all of the BI<*> 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 does not default to enabling --with=python-support +=item - + +All of the BI<*> debhelper programs and B set +environment variables listed by B, unless +they are already set. They support DEB_BUILD_OPTIONS=noopt too. + =back =back -- cgit v1.2.1