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 34a16a3512d8c2b65e0355f87e3bfb7261d1bad1..a896bb54dda1553c21e9ad4a737113d6a637519b 100644 (file)
--- a/debhelper.pod
+++ b/debhelper.pod
@@ -195,6 +195,8 @@ 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
 
@@ -472,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 -