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
Do not act on the specified package even if an -a, -i, or -p option lists
the package as one that should be acted on.
+=item B<--ignore=>I<file>
+
+Ignore the specified file. This can be used if debian/ contains a debhelper
+config file that a debhelper command should not act on. Note that
+debian/compat, debian/control, and debian/changelog can't be ignored, but
+then, there should never be a reason to ignore those files.
+
+For example, if upstream ships a debian/init that you don't want
+dh_installinit to install, use --ignore=debian/init
+
=item B<-P>I<tmpdir>, B<--tmpdir=>I<tmpdir>
Use "tmpdir" for package build directory. The default is debian/<package>
% 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:
=item V5
-This is the recommended mode of operation. It does everything V4 does,
-plus:
+Changes from V4 are:
=over 8
dh_installdocs skips installing empty files.
+=item -
+
+dh_install errors out if wildcards expand to nothing.
+
+=back
+
+=item V6
+
+This is the recommended mode of operation. It does everything V5 does,
+plus:
+
+=over 8
+
+=item -
+
+Commands that generate maintainer script fragements will order the
+fragements in reverse order for the prerm and postrm scripts.
+
+=item -
+
+dh_installwm will install a slave manpage link for x-window-manager.1.gz,
+if it sees the man page in usr/share/man/man1 in the package build
+directory.
+
+=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:.git". 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
=back
debhelper to your Build-Depends line in debian/control. You should
build-depend on a version of debhelper equal to (or greater than) the
debhelper compatibility level your package uses. So if your package used
-compatibility level 5:
+compatibility level 6:
- Build-Depends: debhelper (>= 5)
+ Build-Depends: debhelper (>= 6)
=head1 ENVIRONMENT
A set of example debian/rules files that use debhelper.
-=item L<http://kitenet.net/programs/debhelper/>
+=item L<http://kitenet.net/~joey/code/debhelper/>
Debhelper web site.