summaryrefslogtreecommitdiff
path: root/dh
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2011-05-21 15:25:49 -0400
committerJoey Hess <joey@kitenet.net>2011-05-21 15:37:58 -0400
commit5e13cc10b6c899fa143b76d4b312b7cdb2e39d08 (patch)
tree8a375bfe1c716044e38d585d2d29f27ea04f7c90 /dh
parentfbe972f2a63a1dd6d7a49c63cb705e688adf27f0 (diff)
Fix example. Closes: #627534
Diffstat (limited to 'dh')
-rwxr-xr-xdh11
1 files changed, 7 insertions, 4 deletions
diff --git a/dh b/dh
index 921ef55..50e0f14 100755
--- a/dh
+++ b/dh
@@ -240,16 +240,19 @@ L<dh_listpackages(1)> to test what is being built. For example:
endif
Finally, remember that you are not limited to using override targets in the
-rules file when using B<dh>. You can also explicitly define any of the regular
+rules file when using B<dh>. You can also explicitly define the regular
rules file targets when it makes sense to do so. A common reason to do this
-is if your package needs different B<build-arch> and B<build-indep> targets. For
-example, a package with a long document build process can put it in
-B<build-indep> to avoid build daemons redundantly building the documentation.
+is if your package needs different B<build-arch> and B<build-indep> targets.
+For example, a package with a long document build process can put it in
+B<build-indep>.
#!/usr/bin/make -f
%:
dh $@
+ binary: binary-arch binary-indep ;
+ binary-arch:: build-arch
+ binary-indep:: build-indep
build: build-arch build-indep ;
build-indep:
$(MAKE) docs