In some rare cases, you may want to have different versions of these files
for different architectures. If files named debian/package.foo.arch
-exist, where "arch" is the same as the output of "dpkg --print-architecture",
+exist, where "arch" is the same as the output of
+"dpkg-architecture -qDEB_HOST_ARCH",
then they will be used in preference to other, more general files.
In many cases, these config files are used to specify various types of
% echo 5 > debian/compat
Unless otherwise indicated, all debhelper documentation assumes that you
-are using the most recent compatability level, and in most cases does not
-indicate if the behavior is different in an earlier compatability level, so
-if you are not using the most recent compatability level, you're advised to
-read below for notes about what is different in earlier compatability
+are using the most recent compatibility level, and in most cases does not
+indicate if the behavior is different in an earlier compatibility level, so
+if you are not using the most recent compatibility level, you're advised to
+read below for notes about what is different in earlier compatibility
levels.
These are the available compatibility levels:
dh_installdocs skips installing empty files.
+=item -
+
+dh_install errors out if wildcards expand to nothing.
+
=back
+=item V6
+
+This mode is still under development. Currently it has these differences
+compared to V5:
+
+=over 8
+
+=item -
+
+dh_installwm will install a slave manpage link for x-window-manager.1.gz.
+
+=item -
+
+dh_builddeb did not previously delete everything matching
+DH_ALWAYS_EXCLUDE, if it was set to a list of things to exclude, such as
+"CVS:.svn". Now it does.
+
+=item -
+
+dh_installman allows overwriting existing man pages in the package build
+directory. In previous compatability levels it silently refuses to do this.
+
=back
=head2 Doc directory symlinks