doc tweak re target dependencies

If a rules file has a custom install or binary target, those targets
still need to explicitly depend on the build target. Unless dh is used
in such a target (which it probably is of course).

It's not possible to avoid the need for those dependencies. A rules file
with a hand-written binary target simply does not run dh, so dh can
do nothing to help it run the build target.

Reword the docs to not give the wrong impression that dh somehow
magically makes that work.

diff --git a/debhelper.pod b/debhelper.pod
index 45d9241f5cb8ecc52a102d42f3fc3d020ccc4aec..9000d69aa63991810b1bc98aefc943bd9f328680 100644 (file)
--- a/debhelper.pod
+++ b/debhelper.pod
@@ -476,8 +476,9 @@ multiarch directories to autoconf in --libdir and --libexecdir.
 
 =item -
 
-dh supports use of standard targets in debian/rules without needing
-to manually define the dependencies between targets there.
+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.
 
 =item -
 

diff --git a/dh b/dh
index 68f3d79ee6c625b2bab205baa8a25f44030c481f..bf9685d7f9a53a6f21e16f3e6947d1501b9b1bf4 100755 (executable)
--- a/dh
+++ b/dh
@@ -258,7 +258,7 @@ B<build-indep>.
 
 Note that in the example above, dh will arrange for "debian/rules build"
 to call your build-indep and build-arch targets. You do not need to
-explicitly define the dependencies in the rules file when using dh with
+explicitly define those dependencies in the rules file when using dh with
 compatibility level v9. This example would be more complicated with
 earlier compatibility levels.