Mention in debhelper(7) that buildsystem options are typically passed to dh. Closes...

[debhelper.git] / debhelper.pod

diff --git a/debhelper.pod b/debhelper.pod
index 9000d69aa63991810b1bc98aefc943bd9f328680..a896bb54dda1553c21e9ad4a737113d6a637519b 100644 (file)
--- a/debhelper.pod
+++ b/debhelper.pod
@@ -191,14 +191,12 @@ 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.
 You can use these command line options to override the default behavior.
+Typically these are passed to L<dh(1)>, which then passes them to all the 
+B<dh_auto_>I<*> programs.
 
 =over 4
 
@@ -476,9 +474,10 @@ multiarch directories to autoconf in --libdir and --libexecdir.
 
 =item -
 
-dh allows defining custom build, build-arch, and build-indep targets
-in debian/rules, without needing to manually define the other targets
-that depend on them.
+dh is aware of the usual dependencies between targets in debian/rules.
+So, "dh binary" will run any build, build-arch, build-indep, install,
+etc targets that exist in the rules file. There's no need to define an
+explicit binary target with explicit dependencies on the other targets.
 
 =item -
 
@@ -489,6 +488,12 @@ in --libexecdir when using autoconf.
 
 B<dh> does not default to enabling --with=python-support
 
+=item -
+
+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.
+
 =back
 
 =back