Fix example. Closes: #627534

[debhelper.git] / dh

diff --git a/dh b/dh
index 9e6fa04e65d8d1e3dde932690d6f0c232576a94b..50e0f14dbd90895295b82c98d08627da0aba349b 100755 (executable)
--- 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
@@ -360,7 +363,9 @@ my @i = qw{
        dh_installudev
        dh_installwm
        dh_installxfonts
+       dh_installgsettings
        dh_bugfiles
+       dh_ucf
        dh_lintian
        dh_gconf
        dh_icons
@@ -689,8 +694,8 @@ sub run {
                        if ($override_command ne 'dh_clean') {
                                my %packages=map { $_ => 1 } @packages;
                                map { delete $packages{$_} } @exclude;
-                               commit_override_log(keys %packages);
                                write_log($override_command, keys %packages);
+                               commit_override_log(keys %packages);
                        }
 
                        delete $ENV{DH_INTERNAL_OPTIONS};