summaryrefslogtreecommitdiff
path: root/debhelper.pod
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2011-07-19 23:20:08 -0400
committerJoey Hess <joey@kitenet.net>2011-07-19 23:24:52 -0400
commit6693ccf9146d8d9bb29e99276f6e30af3eab02c2 (patch)
tree2552f11781f768c6c85a991d8202e9fc5869b06c /debhelper.pod
parentd63e08f7ced8f182355038c52babf2f99014f04b (diff)
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.
Diffstat (limited to 'debhelper.pod')
-rw-r--r--debhelper.pod5
1 files changed, 3 insertions, 2 deletions
diff --git a/debhelper.pod b/debhelper.pod
index 45d9241..9000d69 100644
--- 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 -