+#. type: textblock
+#: dh:207
+msgid ""
+"Here is a way to prevent dh from running several commands that you don't "
+"want it to run, by defining empty override targets for each command."
+msgstr ""
+
+#. type: verbatim
+#: dh:210 dh:221 dh:238
+#, no-wrap
+msgid ""
+"\t#!/usr/bin/make -f\n"
+"\t%:\n"
+"\t\tdh $@\n"
+"\t\n"
+msgstr ""
+
+#. type: verbatim
+#: dh:214
+#, no-wrap
+msgid ""
+"\t# Commands not to run:\n"
+"\toverride_dh_auto_test override_dh_compress override_dh_fixperms:\n"
+"\n"
+msgstr ""
+
+#. type: textblock
+#: dh:217
+msgid ""
+"Sometimes, you may need to make an override target only run commands when a "
+"particular package is being built. This can be accomplished using "
+"L<dh_listpackages(1)> to test what is being built. For example:"
+msgstr ""
+
+#. type: verbatim
+#: dh:225
+#, no-wrap
+msgid ""
+"\toverride_dh_fixperms:\n"
+"\t\tdh_fixperms\n"
+"\tifneq (,$(findstring foo, $(shell dh_listpackages)))\n"
+"\t\tchmod 4755 debian/foo/usr/bin/foo\n"
+"\tendif\n"
+"\n"
+msgstr ""
+
+#. type: textblock
+#: dh:231
+msgid ""
+"Finally, remember that you are not limited to using override targets in the "
+"rules file when using dh. You can also explicitly define any of the regular "
+"rules file targets when it makes sense to do so. A common reason to do this "
+"is if your package needs different build-arch and build-indep targets. For "
+"example, a package with a long document build process can put it in build-"
+"indep to avoid build daemons redundantly building the documentation."
+msgstr ""
+
+#. type: verbatim
+#: dh:242
+#, no-wrap
+msgid ""
+"\tbuild: build-arch build-indep ;\n"
+"\tbuild-indep:\n"
+"\t\t$(MAKE) docs\n"
+"\tbuild-arch:\n"
+"\t\t$(MAKE) bins\n"
+"\n"
+msgstr ""
+
+#. type: =head1
+#: dh:248
+msgid "INTERNALS"
+msgstr ""
+
+#. type: textblock
+#: dh:250
+msgid ""
+"If you're curious about dh's internals, here's how it works under the hood."
+msgstr ""
+
+#. type: textblock
+#: dh:252
+msgid ""
+"Each debhelper command will record when it's successfully run in debian/"
+"package.debhelper.log. (Which dh_clean deletes.) So dh can tell which "
+"commands have already been run, for which packages, and skip running those "
+"commands again."
+msgstr ""
+
+#. type: textblock
+#: dh:257
+msgid ""
+"Each time dh is run, it examines the log, and finds the last logged command "
+"that is in the specified sequence. It then continues with the next command "
+"in the sequence. The B<--until>, B<--before>, B<--after>, and B<--remaining> "
+"options can override this behavior."
+msgstr ""
+
+#. type: textblock
+#: dh:262
+msgid ""
+"dh uses the DH_INTERNAL_OPTIONS environment variable to pass information "
+"through to debhelper commands that are run inside override targets. The "
+"contents (and indeed, existence) of this environment variable, as the name "
+"might suggest, is subject to change at any time."
+msgstr ""
+