.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.28)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\" nothing in troff, for use with C<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{
.    if \nF \{
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "debhelper 7"
.TH debhelper 7 "2017-02-18" "10.2.5~bpo8+1" "Debhelper"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "NAME"
debhelper \- the debhelper tool suite
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
\&\fBdh_\fR\fI*\fR [\fB\-v\fR] [\fB\-a\fR] [\fB\-i\fR] [\fB\-\-no\-act\fR] [\fB\-p\fR\fIpackage\fR] [\fB\-N\fR\fIpackage\fR] [\fB\-P\fR\fItmpdir\fR]
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
Debhelper is used to help you build a Debian package. The philosophy behind
debhelper is to provide a collection of small, simple, and easily
understood tools that are used in \fIdebian/rules\fR to automate various common
aspects of building a package. This means less work for you, the packager.
It also, to some degree means that these tools can be changed if Debian
policy changes, and packages that use them will require only a rebuild to
comply with the new policy.
.PP
A typical \fIdebian/rules\fR file that uses debhelper will call several debhelper
commands in sequence, or use \fIdh\fR\|(1) to automate this process. Examples of
rules files that use debhelper are in \fI/usr/share/doc/debhelper/examples/\fR
.PP
To create a new Debian package using debhelper, you can just copy one of
the sample rules files and edit it by hand. Or you can try the \fBdh-make\fR
package, which contains a dh_make command that partially
automates the process. For a more gentle introduction, the \fBmaint-guide\fR Debian 
package contains a tutorial about making your first package using debhelper.
.SH "DEBHELPER COMMANDS"
.IX Header "DEBHELPER COMMANDS"
Here is the list of debhelper commands you can use. See their man
pages for additional documentation.
.IP "\fIdh_auto_build\fR\|(1)" 4
.IX Item "dh_auto_build"
automatically builds a package
.IP "\fIdh_auto_clean\fR\|(1)" 4
.IX Item "dh_auto_clean"
automatically cleans up after a build
.IP "\fIdh_auto_configure\fR\|(1)" 4
.IX Item "dh_auto_configure"
automatically configure a package prior to building
.IP "\fIdh_auto_install\fR\|(1)" 4
.IX Item "dh_auto_install"
automatically runs make install or similar
.IP "\fIdh_auto_test\fR\|(1)" 4
.IX Item "dh_auto_test"
automatically runs a package's test suites
.IP "\fIdh_bugfiles\fR\|(1)" 4
.IX Item "dh_bugfiles"
install bug reporting customization files into package build directories
.IP "\fIdh_builddeb\fR\|(1)" 4
.IX Item "dh_builddeb"
build Debian binary packages
.IP "\fIdh_clean\fR\|(1)" 4
.IX Item "dh_clean"
clean up package build directories
.IP "\fIdh_compress\fR\|(1)" 4
.IX Item "dh_compress"
compress files and fix symlinks in package build directories
.IP "\fIdh_fixperms\fR\|(1)" 4
.IX Item "dh_fixperms"
fix permissions of files in package build directories
.IP "\fIdh_gconf\fR\|(1)" 4
.IX Item "dh_gconf"
install GConf defaults files and register schemas
.IP "\fIdh_gencontrol\fR\|(1)" 4
.IX Item "dh_gencontrol"
generate and install control file
.IP "\fIdh_icons\fR\|(1)" 4
.IX Item "dh_icons"
Update caches of Freedesktop icons
.IP "\fIdh_install\fR\|(1)" 4
.IX Item "dh_install"
install files into package build directories
.IP "\fIdh_installcatalogs\fR\|(1)" 4
.IX Item "dh_installcatalogs"
install and register \s-1SGML\s0 Catalogs
.IP "\fIdh_installchangelogs\fR\|(1)" 4
.IX Item "dh_installchangelogs"
install changelogs into package build directories
.IP "\fIdh_installcron\fR\|(1)" 4
.IX Item "dh_installcron"
install cron scripts into etc/cron.*
.IP "\fIdh_installdeb\fR\|(1)" 4
.IX Item "dh_installdeb"
install files into the \s-1DEBIAN\s0 directory
.IP "\fIdh_installdebconf\fR\|(1)" 4
.IX Item "dh_installdebconf"
install files used by debconf in package build directories
.IP "\fIdh_installdirs\fR\|(1)" 4
.IX Item "dh_installdirs"
create subdirectories in package build directories
.IP "\fIdh_installdocs\fR\|(1)" 4
.IX Item "dh_installdocs"
install documentation into package build directories
.IP "\fIdh_installemacsen\fR\|(1)" 4
.IX Item "dh_installemacsen"
register an Emacs add on package
.IP "\fIdh_installexamples\fR\|(1)" 4
.IX Item "dh_installexamples"
install example files into package build directories
.IP "\fIdh_installgsettings\fR\|(1)" 4
.IX Item "dh_installgsettings"
install GSettings overrides and set dependencies
.IP "\fIdh_installifupdown\fR\|(1)" 4
.IX Item "dh_installifupdown"
install if-up and if-down hooks
.IP "\fIdh_installinfo\fR\|(1)" 4
.IX Item "dh_installinfo"
install info files
.IP "\fIdh_installinit\fR\|(1)" 4
.IX Item "dh_installinit"
install service init files into package build directories
.IP "\fIdh_installlogcheck\fR\|(1)" 4
.IX Item "dh_installlogcheck"
install logcheck rulefiles into etc/logcheck/
.IP "\fIdh_installlogrotate\fR\|(1)" 4
.IX Item "dh_installlogrotate"
install logrotate config files
.IP "\fIdh_installman\fR\|(1)" 4
.IX Item "dh_installman"
install man pages into package build directories
.IP "\fIdh_installmenu\fR\|(1)" 4
.IX Item "dh_installmenu"
install Debian menu files into package build directories
.IP "\fIdh_installmime\fR\|(1)" 4
.IX Item "dh_installmime"
install mime files into package build directories
.IP "\fIdh_installmodules\fR\|(1)" 4
.IX Item "dh_installmodules"
register kernel modules
.IP "\fIdh_installpam\fR\|(1)" 4
.IX Item "dh_installpam"
install pam support files
.IP "\fIdh_installppp\fR\|(1)" 4
.IX Item "dh_installppp"
install ppp ip-up and ip-down files
.IP "\fIdh_installudev\fR\|(1)" 4
.IX Item "dh_installudev"
install udev rules files
.IP "\fIdh_installwm\fR\|(1)" 4
.IX Item "dh_installwm"
register a window manager
.IP "\fIdh_installxfonts\fR\|(1)" 4
.IX Item "dh_installxfonts"
register X fonts
.IP "\fIdh_link\fR\|(1)" 4
.IX Item "dh_link"
create symlinks in package build directories
.IP "\fIdh_lintian\fR\|(1)" 4
.IX Item "dh_lintian"
install lintian override files into package build directories
.IP "\fIdh_listpackages\fR\|(1)" 4
.IX Item "dh_listpackages"
list binary packages debhelper will act on
.IP "\fIdh_makeshlibs\fR\|(1)" 4
.IX Item "dh_makeshlibs"
automatically create shlibs file and call dpkg-gensymbols
.IP "\fIdh_md5sums\fR\|(1)" 4
.IX Item "dh_md5sums"
generate DEBIAN/md5sums file
.IP "\fIdh_movefiles\fR\|(1)" 4
.IX Item "dh_movefiles"
move files out of debian/tmp into subpackages
.IP "\fIdh_perl\fR\|(1)" 4
.IX Item "dh_perl"
calculates Perl dependencies and cleans up after MakeMaker
.IP "\fIdh_prep\fR\|(1)" 4
.IX Item "dh_prep"
perform cleanups in preparation for building a binary package
.IP "\fIdh_shlibdeps\fR\|(1)" 4
.IX Item "dh_shlibdeps"
calculate shared library dependencies
.IP "\fIdh_strip\fR\|(1)" 4
.IX Item "dh_strip"
strip executables, shared libraries, and some static libraries
.IP "\fIdh_systemd_enable\fR\|(1)" 4
.IX Item "dh_systemd_enable"
enable/disable systemd unit files
.IP "\fIdh_systemd_start\fR\|(1)" 4
.IX Item "dh_systemd_start"
start/stop/restart systemd unit files
.IP "\fIdh_testdir\fR\|(1)" 4
.IX Item "dh_testdir"
test directory before building Debian package
.IP "\fIdh_testroot\fR\|(1)" 4
.IX Item "dh_testroot"
ensure that a package is built as root
.IP "\fIdh_ucf\fR\|(1)" 4
.IX Item "dh_ucf"
register configuration files with ucf
.IP "\fIdh_update_autotools_config\fR\|(1)" 4
.IX Item "dh_update_autotools_config"
Update autotools config files
.IP "\fIdh_usrlocal\fR\|(1)" 4
.IX Item "dh_usrlocal"
migrate usr/local directories to maintainer scripts
.SS "Deprecated Commands"
.IX Subsection "Deprecated Commands"
A few debhelper commands are deprecated and should not be used.
.IP "\fIdh_installmanpages\fR\|(1)" 4
.IX Item "dh_installmanpages"
old-style man page installer (deprecated)
.SS "Other Commands"
.IX Subsection "Other Commands"
If a program's name starts with \fBdh_\fR, and the program is not on the above
lists, then it is not part of the debhelper package, but it should still
work like the other programs described on this page.
.SH "DEBHELPER CONFIG FILES"
.IX Header "DEBHELPER CONFIG FILES"
Many debhelper commands make use of files in \fIdebian/\fR to control what they
do. Besides the common \fIdebian/changelog\fR and \fIdebian/control\fR, which are
in all packages, not just those using debhelper, some additional files can
be used to configure the behavior of specific debhelper commands. These
files are typically named debian/\fIpackage\fR.foo (where \fIpackage\fR of course,
is replaced with the package that is being acted on).
.PP
For example, \fBdh_installdocs\fR uses files named \fIdebian/package.docs\fR to list
the documentation files it will install. See the man pages of individual
commands for details about the names and formats of the files they use.
Generally, these files will list files to act on, one file per line. Some
programs in debhelper use pairs of files and destinations or slightly more
complicated formats.
.PP
Note for the first (or only) binary package listed in
\&\fIdebian/control\fR, debhelper will use \fIdebian/foo\fR when there's no
\&\fIdebian/package.foo\fR file.
.PP
In some rare cases, you may want to have different versions of these files
for different architectures or OSes. If files named debian/\fIpackage\fR.foo.\fI\s-1ARCH\s0\fR
or debian/\fIpackage\fR.foo.\fI\s-1OS\s0\fR exist, where \fI\s-1ARCH\s0\fR and \fI\s-1OS\s0\fR are the same as the
output of "\fBdpkg-architecture \-qDEB_HOST_ARCH\fR\*(L" /
\&\*(R"\fBdpkg-architecture \-qDEB_HOST_ARCH_OS\fR",
then they will be used in preference to other, more general files.
.PP
Mostly, these config files are used to specify lists of various types of
files. Documentation or example files to install, files to move, and so on.
When appropriate, in cases like these, you can use standard shell wildcard
characters (\fB?\fR and \fB*\fR and \fB[\fR\fI..\fR\fB]\fR character classes) in the files.
You can also put comments in these files; lines beginning with \fB#\fR are
ignored.
.PP
The syntax of these files is intentionally kept very simple to make them
easy to read, understand, and modify. If you prefer power and complexity,
you can make the file executable, and write a program that outputs
whatever content is appropriate for a given situation. When you do so,
the output is not further processed to expand wildcards or strip comments.
.SH "SHARED DEBHELPER OPTIONS"
.IX Header "SHARED DEBHELPER OPTIONS"
The following command line options are supported by all debhelper programs.
.IP "\fB\-v\fR, \fB\-\-verbose\fR" 4
.IX Item "-v, --verbose"
Verbose mode: show all commands that modify the package build directory.
.IP "\fB\-\-no\-act\fR" 4
.IX Item "--no-act"
Do not really do anything. If used with \-v, the result is that the command
will output what it would have done.
.IP "\fB\-a\fR, \fB\-\-arch\fR" 4
.IX Item "-a, --arch"
Act on architecture dependent packages that should be built for the
\&\fB\s-1DEB_HOST_ARCH\s0\fR architecture.
.IP "\fB\-i\fR, \fB\-\-indep\fR" 4
.IX Item "-i, --indep"
Act on all architecture independent packages.
.IP "\fB\-p\fR\fIpackage\fR, \fB\-\-package=\fR\fIpackage\fR" 4
.IX Item "-ppackage, --package=package"
Act on the package named \fIpackage\fR. This option may be specified multiple
times to make debhelper operate on a given set of packages.
.IP "\fB\-s\fR, \fB\-\-same\-arch\fR" 4
.IX Item "-s, --same-arch"
Deprecated alias of \fB\-a\fR.
.IP "\fB\-N\fR\fIpackage\fR, \fB\-\-no\-package=\fR\fIpackage\fR" 4
.IX Item "-Npackage, --no-package=package"
Do not act on the specified package even if an \fB\-a\fR, \fB\-i\fR, or \fB\-p\fR option lists
the package as one that should be acted on.
.IP "\fB\-\-remaining\-packages\fR" 4
.IX Item "--remaining-packages"
Do not act on the packages which have already been acted on by this debhelper
command earlier (i.e. if the command is present in the package debhelper log).
For example, if you need to call the command with special options only for a
couple of binary packages, pass this option to the last call of the command to
process the rest of packages with default settings.
.IP "\fB\-\-ignore=\fR\fIfile\fR" 4
.IX Item "--ignore=file"
Ignore the specified file. This can be used if \fIdebian/\fR contains a debhelper
config file that a debhelper command should not act on. Note that
\&\fIdebian/compat\fR, \fIdebian/control\fR, and \fIdebian/changelog\fR can't be ignored, but
then, there should never be a reason to ignore those files.
.Sp
For example, if upstream ships a \fIdebian/init\fR that you don't want
\&\fBdh_installinit\fR to install, use \fB\-\-ignore=debian/init\fR
.IP "\fB\-P\fR\fItmpdir\fR, \fB\-\-tmpdir=\fR\fItmpdir\fR" 4
.IX Item "-Ptmpdir, --tmpdir=tmpdir"
Use \fItmpdir\fR for package build directory. The default is debian/\fIpackage\fR
.IP "\fB\-\-mainpackage=\fR\fIpackage\fR" 4
.IX Item "--mainpackage=package"
This little-used option changes the package which debhelper considers the
\&\*(L"main package\*(R", that is, the first one listed in \fIdebian/control\fR, and the
one for which \fIdebian/foo\fR files can be used instead of the usual
\&\fIdebian/package.foo\fR files.
.IP "\fB\-O=\fR\fIoption\fR|\fIbundle\fR" 4
.IX Item "-O=option|bundle"
This is used by \fIdh\fR\|(1) when passing user-specified options to all the
commands it runs. If the command supports the specified option or option
bundle, it will take effect. If the command does not support the option (or
any part of an option bundle), it will be ignored.
.SH "COMMON DEBHELPER OPTIONS"
.IX Header "COMMON DEBHELPER OPTIONS"
The following command line options are supported by some debhelper programs.
See the man page of each program for a complete explanation of what each
option does.
.IP "\fB\-n\fR" 4
.IX Item "-n"
Do not modify \fIpostinst\fR, \fIpostrm\fR, etc. scripts.
.IP "\fB\-X\fR\fIitem\fR, \fB\-\-exclude=\fR\fIitem\fR" 4
.IX Item "-Xitem, --exclude=item"
Exclude an item from processing. This option may be used multiple times,
to exclude more than one thing. The \efIitem\efR is typically part of a
filename, and any file containing the specified text will be excluded.
.IP "\fB\-A\fR, \fB\-\-all\fR" 4
.IX Item "-A, --all"
Makes files or other items that are specified on the command line take effect
in \s-1ALL\s0 packages acted on, not just the first.
.SH "BUILD SYSTEM OPTIONS"
.IX Header "BUILD SYSTEM OPTIONS"
The following command line options are supported by all of the \fBdh_auto_\fR\fI*\fR
debhelper programs. These programs support a variety of build systems,
and normally heuristically determine which to use, and how to use them.
You can use these command line options to override the default behavior.
Typically these are passed to \fIdh\fR\|(1), which then passes them to all the 
\&\fBdh_auto_\fR\fI*\fR programs.
.IP "\fB\-S\fR\fIbuildsystem\fR, \fB\-\-buildsystem=\fR\fIbuildsystem\fR" 4
.IX Item "-Sbuildsystem, --buildsystem=buildsystem"
Force use of the specified \fIbuildsystem\fR, instead of trying to auto-select
one which might be applicable for the package.
.IP "\fB\-D\fR\fIdirectory\fR, \fB\-\-sourcedirectory=\fR\fIdirectory\fR" 4
.IX Item "-Ddirectory, --sourcedirectory=directory"
Assume that the original package source tree is at the specified
\&\fIdirectory\fR rather than the top level directory of the Debian
source package tree.
.IP "\fB\-B\fR[\fIdirectory\fR], \fB\-\-builddirectory=\fR[\fIdirectory\fR]" 4
.IX Item "-B[directory], --builddirectory=[directory]"
Enable out of source building and use the specified \fIdirectory\fR as the build
directory. If \fIdirectory\fR parameter is omitted, a default build directory
will be chosen.
.Sp
If this option is not specified, building will be done in source by default
unless the build system requires or prefers out of source tree building.
In such a case, the default build directory will be used even if
\&\fB\-\-builddirectory\fR is not specified.
.Sp
If the build system prefers out of source tree building but still
allows in source building, the latter can be re-enabled by passing a build
directory path that is the same as the source directory path.
.IP "\fB\-\-parallel\fR, \fB\-\-no\-parallel\fR" 4
.IX Item "--parallel, --no-parallel"
Control whether parallel builds should be used if underlying build
system supports them.  The number of parallel jobs is controlled by
the \fB\s-1DEB_BUILD_OPTIONS\s0\fR environment variable (\*(L"Debian Policy,
section 4.9.1\*(R") at build time. It might also be subject to a build
system specific limit.
.Sp
If neither option is specified, debhelper currently defaults to
\&\fB\-\-parallel\fR in compat 10 (or later) and \fB\-\-no\-parallel\fR otherwise.
.Sp
As an optimization, \fBdh\fR will try to avoid passing these options to
subprocesses, if they are unncessary and the only options passed.
Notably this happens when \fB\s-1DEB_BUILD_OPTIONS\s0\fR does not have a
\&\fIparallel\fR parameter (or its value is 1).
.IP "\fB\-\-max\-parallel=\fR\fImaximum\fR" 4
.IX Item "--max-parallel=maximum"
This option implies \fB\-\-parallel\fR and allows further limiting the number of
jobs that can be used in a parallel build. If the package build is known to
only work with certain levels of concurrency, you can set this to the maximum
level that is known to work, or that you wish to support.
.Sp
Notably, setting the maximum to 1 is effectively the same as using
\&\fB\-\-no\-parallel\fR.
.IP "\fB\-\-list\fR, \fB\-l\fR" 4
.IX Item "--list, -l"
List all build systems supported by debhelper on this system. The list
includes both default and third party build systems (marked as such). Also
shows which build system would be automatically selected, or which one
is manually specified with the \fB\-\-buildsystem\fR option.
.SH "COMPATIBILITY LEVELS"
.IX Header "COMPATIBILITY LEVELS"
From time to time, major non-backwards-compatible changes need to be made
to debhelper, to keep it clean and well-designed as needs change and its
author gains more experience. To prevent such major changes from breaking
existing packages, the concept of debhelper compatibility levels was 
introduced. You must tell debhelper which compatibility level it should use, and
it modifies its behavior in various ways.  The compatibility level is
specified in the \fIdebian/compat\fR file and the file must be present.
.PP
Tell debhelper what compatibility level to use by writing a number to
\&\fIdebian/compat\fR. For example, to use v9 mode:
.PP
.Vb 1
\&  % echo 9 > debian/compat
.Ve
.PP
Your package will also need a versioned build dependency on a version of
debhelper equal to (or greater than) the compatibility level your package
uses. So for compatibility level 9, ensure debian/control has:
.PP
.Vb 1
\&  Build\-Depends: debhelper (>= 9)
.Ve
.PP
Unless otherwise indicated, all debhelper documentation assumes that you
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.
.PP
These are the available compatibility levels:
.IP "v5" 4
.IX Item "v5"
This is the lowest supported compatibility level.
.Sp
If you are upgrading from an earlier compatibility level, please
review \fIdebhelper\-obsolete\-compat\fR\|(7).
.Sp
This mode is deprecated.
.IP "v6" 4
.IX Item "v6"
Changes from v5 are:
.RS 4
.IP "\-" 8
Commands that generate maintainer script fragments will order the
fragments in reverse order for the \fIprerm\fR and \fIpostrm\fR scripts.
.IP "\-" 8
\&\fBdh_installwm\fR will install a slave manpage link for \fIx\-window\-manager.1.gz\fR,
if it sees the man page in \fIusr/share/man/man1\fR in the package build
directory.
.IP "\-" 8
\&\fBdh_builddeb\fR did not previously delete everything matching
\&\fB\s-1DH_ALWAYS_EXCLUDE\s0\fR, if it was set to a list of things to exclude, such as
\&\fB\s-1CVS:\s0.svn:.git\fR. Now it does.
.IP "\-" 8
\&\fBdh_installman\fR allows overwriting existing man pages in the package build
directory. In previous compatibility levels it silently refuses to do this.
.RE
.RS 4
.Sp
This mode is deprecated.
.RE
.IP "v7" 4
.IX Item "v7"
Changes from v6 are:
.RS 4
.IP "\-" 8
\&\fBdh_install\fR, will fall back to looking for files in \fIdebian/tmp\fR if it doesn't
find them in the current directory (or wherever you tell it look using
\&\fB\-\-sourcedir\fR). This allows \fBdh_install\fR to interoperate with \fBdh_auto_install\fR,
which installs to \fIdebian/tmp\fR, without needing any special parameters.
.IP "\-" 8
\&\fBdh_clean\fR will read \fIdebian/clean\fR and delete files listed there.
.IP "\-" 8
\&\fBdh_clean\fR will delete toplevel \fI*\-stamp\fR files.
.IP "\-" 8
\&\fBdh_installchangelogs\fR will guess at what file is the upstream changelog if
none is specified.
.RE
.RS 4
.Sp
This mode is deprecated.
.RE
.IP "v8" 4
.IX Item "v8"
Changes from v7 are:
.RS 4
.IP "\-" 8
Commands will fail rather than warning when they are passed unknown options.
.IP "\-" 8
\&\fBdh_makeshlibs\fR will run \fBdpkg-gensymbols\fR on all shared libraries that it
generates shlibs files for. So \fB\-X\fR can be used to exclude libraries.
Also, libraries in unusual locations that \fBdpkg-gensymbols\fR would not
have processed before will be passed to it, a behavior change that 
can cause some packages to fail to build.
.IP "\-" 8
\&\fBdh\fR requires the sequence to run be specified as the first parameter, and
any switches come after it. Ie, use "\fBdh $@ \-\-foo\fR\*(L", not \*(R"\fBdh \-\-foo $@\fR".
.IP "\-" 8
\&\fBdh_auto_\fR\fI*\fR prefer to use Perl's \fBModule::Build\fR in preference to \fIMakefile.PL\fR.
.RE
.RS 4
.Sp
This mode is deprecated.
.RE
.IP "v9" 4
.IX Item "v9"
Changes from v8 are:
.RS 4
.IP "\-" 8
Multiarch support. In particular, \fBdh_auto_configure\fR passes
multiarch directories to autoconf in \-\-libdir and \-\-libexecdir.
.IP "\-" 8
dh is aware of the usual dependencies between targets in debian/rules.
So, \*(L"dh binary\*(R" will run any build, build-arch, build-indep, install,
etc targets that exist in the rules file. There's no need to define an
explicit binary target with explicit dependencies on the other targets.
.IP "\-" 8
\&\fBdh_strip\fR compresses debugging symbol files to reduce the installed
size of \-dbg packages.
.IP "\-" 8
\&\fBdh_auto_configure\fR does not include the source package name
in \-\-libexecdir when using autoconf.
.IP "\-" 8
\&\fBdh\fR does not default to enabling \-\-with=python\-support
.IP "\-" 8
All of the \fBdh_auto_\fR\fI*\fR debhelper programs and \fBdh\fR set
environment variables listed by \fBdpkg-buildflags\fR, unless
they are already set.
.IP "\-" 8
\&\fBdh_auto_configure\fR passes \fBdpkg-buildflags\fR \s-1CFLAGS, CPPFLAGS,\s0 and
\&\s-1LDFLAGS\s0 to perl \fIMakefile.PL\fR and \fIBuild.PL\fR
.IP "\-" 8
\&\fBdh_strip\fR puts separated debug symbols in a location based on their
build-id.
.IP "\-" 8
Executable debhelper config files are run and their output used as the
configuration.
.RE
.RS 4
.RE
.IP "v10" 4
.IX Item "v10"
This is the recommended mode of operation.
.Sp
Changes from v9 are:
.RS 4
.IP "\-" 8
\&\fBdh_installinit\fR will no longer install a file named debian/\fIpackage\fR
as an init script.
.IP "\-" 8
\&\fBdh_installdocs\fR will error out if it detects links created with
\&\-\-link\-doc between packages of architecture \*(L"all\*(R" and non\-\*(L"all\*(R" as it
breaks binNMUs.
.IP "\-" 8
\&\fBdh\fR no longer creates the package build directory when skipping
running debhelper commands. This will not affect packages that only build
with debhelper commands, but it may expose bugs in commands not included in
debhelper.
.IP "\-" 8
\&\fBdh_installdeb\fR no longer installs a maintainer-provided
debian/\fIpackage\fR.shlibs file.  This is now done by \fBdh_makeshlibs\fR
instead.
.IP "\-" 8
\&\fBdh_installwm\fR refuses to create a broken package if no man page
can be found (required to register for the x\-window-manager alternative).
.IP "\-" 8
Debhelper will default to \fB\-\-parallel\fR for all buildsystems that
support parallel building.  This can be disabled by using either
\&\fB\-\-no\-parallel\fR or passing \fB\-\-max\-parallel\fR with a value of 1.
.IP "\-" 8
The \fBdh\fR command will not accept any of the deprecated \*(L"manual
sequence control\*(R" parameters (\fB\-\-before\fR, \fB\-\-after\fR, etc.).  Please
use override targets instead.
.IP "\-" 8
The \fBdh\fR command will no longer use log files to track which commands
have been run.  The \fBdh\fR command \fIstill\fR keeps track of whether it
already ran the \*(L"build\*(R" sequence and skip it if it did.
.Sp
The main effects of this are:
.RS 8
.IP "\-" 4
With this, it is now easier to debug the \fIinstall\fR or/and \fIbinary\fR
sequences because they can now trivially be re-run (without having to
do a full \*(L"clean and rebuild\*(R" cycle)
.IP "\-" 4
The main caveat is that \fBdh_*\fR now only keeps track of what happened
in a single override target.  When all the calls to a given \fBdh_cmd\fR
command happens in the same override target everything will work as
before.
.Sp
Example of where it can go wrong:
.Sp
.Vb 2
\&  override_dh_foo:
\&    dh_foo \-pmy\-pkg
\&
\&  override_dh_bar:
\&    dh_bar
\&    dh_foo \-\-remaining
.Ve
.Sp
In this case, the call to \fBdh_foo \-\-remaining\fR will \fIalso\fR include
\&\fImy-pkg\fR, since \fBdh_foo \-pmy\-pkg\fR was run in a separate override
target.  This issue is not limited to \fB\-\-remaining\fR, but also includes
\&\fB\-a\fR, \fB\-i\fR, etc.
.RE
.RS 8
.RE
.IP "\-" 8
The \fBdh_installdeb\fR command now shell-escapes the lines in the
\&\fImaintscript\fR config file.  This was the original intent but it did
not work properly and packages have begun to rely on the incomplete
shell escaping (e.g. quoting file names).
.IP "\-" 8
The \fBdh_installinit\fR command now defaults to
\&\fB\-\-restart\-after\-upgrade\fR.  For packages needing the previous
behaviour, please use \fB\-\-no\-restart\-after\-upgrade\fR.
.IP "\-" 8
The \fBautoreconf\fR sequence is now enabled by default.  Please pass
\&\fB\-\-without autoreconf\fR to \fBdh\fR if this is not desirable for a given
package
.IP "\-" 8
The \fBsystemd\fR sequence is now enabled by default.  Please pass
\&\fB\-\-without systemd\fR to \fBdh\fR if this is not desirable for a given
package.
.RE
.RS 4
.RE
.IP "v11" 4
.IX Item "v11"
This compatibility level is still open for development; use with caution.
.Sp
Changes from v10 are:
.RS 4
.IP "\-" 8
\&\fBdh_installmenu\fR no longer installs \fImenu\fR files.  The
\&\fImenu-method\fR files are still installed.
.IP "\-" 8
\&\fBdh_installinit\fR no longer installs \fIservice\fR or \fItmpfile\fR files, nor
generates maintainer scripts for those files. Use \fBdh_systemd_enable\fR and
\&\fBdh_systemd_start\fR instead.
.IP "\-" 8
The \fB\-s\fR (\fB\-\-same\-arch\fR) option is removed.
.IP "\-" 8
Invoking \fBdh_clean \-k\fR now causes an error instead of a deprecation
warning.
.IP "\-" 8
\&\fBdh_installdocs\fR now installs user-supplied documentation
(e.g. debian/\fIpackage\fR.docs) into \fI/usr/share/doc/mainpackage\fR
rather than \fI/usr/share/doc/package\fR by default as recommended by
Debian Policy 3.9.7.
.Sp
If you need the old behaviour, it can be emulated by using the
\&\fB\-\-mainpackage\fR option.
.Sp
Please remember to check/update your doc-base files.
.IP "\-" 8
\&\fBdh_installdirs\fR no longer creates debian/\fIpackage\fR directories
unless explicitly requested (or it has to create a subdirectory in
it).
.Sp
The vast majority of all packages will be unaffected by this change.
.IP "\-" 8
\&\fBdh\fR no longer creates a stamp (or log) file to record whether the
build already ran or not.  This means that unless upstream's build
system correctly tracks this, the build will be run twice (once for
the \*(L"build\*(R" target and once for the \*(L"binary\*(R" target).
.Sp
On the other hand, this means that rebuild without cleaning
(e.g. \fBdpkg-buildpackage \-nc\fR) will behave as most people would
expect.
.Sp
The previous behaviour can restored by using \fB\-\-with build-stamp\fR
.RE
.RS 4
.RE
.SS "Participating in the open beta testing of new compat levels"
.IX Subsection "Participating in the open beta testing of new compat levels"
It is possible to opt-in to the open beta testing of new compat
levels.  This is done by setting the compat level to the string
\&\*(L"beta-tester\*(R".
.PP
Packages using this compat level will automatically be upgraded to the
highest compatibility level in open beta.  In periods without any open
beta versions, the compat level will be the highest stable
compatibility level.
.PP
Please consider the following before opting in:
.IP "\(bu" 4
The automatic upgrade in compatibility level may cause the package (or
a feature in it) to stop functioning.
.IP "\(bu" 4
Compatibility levels in open beta are still subject to change.  We
will try to keep the changes to a minimal once the beta starts.
However, there are no guarantees that the compat will not change
during the beta.
.IP "\(bu" 4
We will notify you via debian\-devel@lists.debian.org before we start a
new open beta compat level.  However, once the beta starts we expect
that you keep yourself up to date on changes to debhelper.
.IP "\(bu" 4
The \*(L"beta-tester\*(R" compatibility version in unstable and testing will
often be different than the one in stable-backports.  Accordingly, it
is not recommended for packages being backported regularly.
.IP "\(bu" 4
You can always opt-out of the beta by resetting the compatibility
level of your package to a stable version.
.PP
Should you still be interested in the open beta testing, please run:
.PP
.Vb 1
\&  % echo beta\-tester > debian/compat
.Ve
.PP
You will also need to ensure that debian/control contains:
.PP
.Vb 1
\&  Build\-Depends: debhelper (>= 9.20160815~)
.Ve
.PP
To ensure that debhelper knows about the \*(L"beta-tester\*(R" compat level.
.SH "NOTES"
.IX Header "NOTES"
.SS "Multiple binary package support"
.IX Subsection "Multiple binary package support"
If your source package generates more than one binary package, debhelper
programs will default to acting on all binary packages when run. If your
source package happens to generate one architecture dependent package, and
another architecture independent package, this is not the correct behavior,
because you need to generate the architecture dependent packages in the
binary-arch \fIdebian/rules\fR target, and the architecture independent packages
in the binary-indep \fIdebian/rules\fR target.
.PP
To facilitate this, as well as give you more control over which packages
are acted on by debhelper programs, all debhelper programs accept the
\&\fB\-a\fR, \fB\-i\fR, \fB\-p\fR, and \fB\-s\fR parameters. These parameters are cumulative. 
If none are given, debhelper programs default to acting on all packages listed
in the control file, with the exceptions below.
.PP
First, any package whose \fBArchitecture\fR field in \fBdebian/control\fR does not
match the \fB\s-1DEB_HOST_ARCH\s0\fR architecture will be excluded
(\*(L"Debian Policy, section 5.6.8\*(R").
.PP
Also, some additional packages may be excluded based on the contents of the
\&\fB\s-1DEB_BUILD_PROFILES\s0\fR environment variable and \fBBuild-Profiles\fR fields in
binary package stanzas in \fBdebian/control\fR, according to the draft policy at
<https://wiki.debian.org/BuildProfileSpec>.
.SS "Automatic generation of Debian install scripts"
.IX Subsection "Automatic generation of Debian install scripts"
Some debhelper commands will automatically generate parts of Debian
maintainer scripts. If you want these automatically generated things
included in your existing Debian maintainer scripts, then you need to add
\&\fB#DEBHELPER#\fR to your scripts, in the place the code should be added.
\&\fB#DEBHELPER#\fR will be replaced by any auto-generated code when you run
\&\fBdh_installdeb\fR.
.PP
If a script does not exist at all and debhelper needs to add something to
it, then debhelper will create the complete script.
.PP
All debhelper commands that automatically generate code in this way let it
be disabled by the \-n parameter (see above).
.PP
Note that the inserted code will be shell code, so you cannot directly use
it in a Perl script. If you would like to embed it into a Perl script, here
is one way to do that (note that I made sure that \f(CW$1\fR, \f(CW$2\fR, etc are set with
the set command):
.PP
.Vb 12
\&  my $temp="set \-e\enset \-\- @ARGV\en" . << \*(AqEOF\*(Aq;
\&  #DEBHELPER#
\&  EOF
\&  if (system($temp)) {
\&     my $exit_code = ($? >> 8) & 0xff;
\&     my $signal = $? & 0x7f;
\&     if ($exit_code) {
\&         die("The debhelper script failed with error code: ${exit_code}");
\&     } else {
\&         die("The debhelper script was killed by signal: ${signal}");
\&     }
\&  }
.Ve
.SS "Automatic generation of miscellaneous dependencies."
.IX Subsection "Automatic generation of miscellaneous dependencies."
Some debhelper commands may make the generated package need to depend on
some other packages. For example, if you use \fIdh_installdebconf\fR\|(1), your
package will generally need to depend on debconf. Or if you use
\&\fIdh_installxfonts\fR\|(1), your package will generally need to depend on a
particular version of xutils. Keeping track of these miscellaneous
dependencies can be annoying since they are dependent on how debhelper does
things, so debhelper offers a way to automate it.
.PP
All commands of this type, besides documenting what dependencies may be
needed on their man pages, will automatically generate a substvar called
\&\fB${misc:Depends}\fR. If you put that token into your \fIdebian/control\fR file, it
will be expanded to the dependencies debhelper figures you need.
.PP
This is entirely independent of the standard \fB${shlibs:Depends}\fR generated by
\&\fIdh_makeshlibs\fR\|(1), and the \fB${perl:Depends}\fR generated by \fIdh_perl\fR\|(1).
You can choose not to use any of these, if debhelper's guesses don't match
reality.
.SS "Package build directories"
.IX Subsection "Package build directories"
By default, all debhelper programs assume that the temporary directory used
for assembling the tree of files in a package is debian/\fIpackage\fR.
.PP
Sometimes, you might want to use some other temporary directory. This is
supported by the \fB\-P\fR flag. For example, "\fBdh_installdocs \-Pdebian/tmp\fR", will
use \fBdebian/tmp\fR as the temporary directory. Note that if you use \fB\-P\fR, the 
debhelper programs can only be acting on a single package at a time. So if 
you have a package that builds many binary packages, you will need to also 
use the \fB\-p\fR flag to specify which binary package the debhelper program will
act on.
.SS "udebs"
.IX Subsection "udebs"
Debhelper includes support for udebs. To create a udeb with debhelper,
add "\fBPackage-Type: udeb\fR" to the package's stanza in \fIdebian/control\fR.
Debhelper will try to create udebs that comply with debian-installer
policy, by making the generated package files end in \fI.udeb\fR, not
installing any documentation into a udeb, skipping over
\&\fIpreinst\fR, \fIpostrm\fR, \fIprerm\fR, and \fIconfig\fR scripts, etc.
.SH "ENVIRONMENT"
.IX Header "ENVIRONMENT"
The following environment variables can influence the behavior of debhelper.
It is important to note that these must be actual environment variables in
order to function properly (not simply \fIMakefile\fR variables). To specify
them properly in \fIdebian/rules\fR, be sure to "\fBexport\fR\*(L" them. For example,
\&\*(R"\fBexport \s-1DH_VERBOSE\s0\fR".
.IP "\fB\s-1DH_VERBOSE\s0\fR" 4
.IX Item "DH_VERBOSE"
Set to \fB1\fR to enable verbose mode. Debhelper will output every command it
runs. Also enables verbose build logs for some build systems like autoconf.
.IP "\fB\s-1DH_QUIET\s0\fR" 4
.IX Item "DH_QUIET"
Set to \fB1\fR to enable quiet mode. Debhelper will not output commands calling
the upstream build system nor will dh print which subcommands are called
and depending on the upstream build system might make that more quiet, too.
This makes it easier to spot important messages but makes the output quite
useless as buildd log.
Ignored if \s-1DH_VERBOSE\s0 is also set.
.IP "\fB\s-1DH_COMPAT\s0\fR" 4
.IX Item "DH_COMPAT"
Temporarily specifies what compatibility level debhelper should run at,
overriding any value in \fIdebian/compat\fR.
.IP "\fB\s-1DH_NO_ACT\s0\fR" 4
.IX Item "DH_NO_ACT"
Set to \fB1\fR to enable no-act mode.
.IP "\fB\s-1DH_OPTIONS\s0\fR" 4
.IX Item "DH_OPTIONS"
Anything in this variable will be prepended to the command line arguments
of all debhelper commands.
.Sp
When using \fIdh\fR\|(1), it can be passed options that will be passed on to each
debhelper command, which is generally better than using \s-1DH_OPTIONS.\s0
.IP "\fB\s-1DH_ALWAYS_EXCLUDE\s0\fR" 4
.IX Item "DH_ALWAYS_EXCLUDE"
If set, this adds the value the variable is set to to the \fB\-X\fR options of all
commands that support the \fB\-X\fR option. Moreover, \fBdh_builddeb\fR will \fBrm \-rf\fR
anything that matches the value in your package build tree.
.Sp
This can be useful if you are doing a build from a \s-1CVS\s0 source tree, in
which case setting \fBDH_ALWAYS_EXCLUDE=CVS\fR will prevent any \s-1CVS\s0 directories
from sneaking into the package you build. Or, if a package has a source
tarball that (unwisely) includes \s-1CVS\s0 directories, you might want to export
\&\fBDH_ALWAYS_EXCLUDE=CVS\fR in \fIdebian/rules\fR, to make it take effect wherever
your package is built.
.Sp
Multiple things to exclude can be separated with colons, as in
\&\fBDH_ALWAYS_EXCLUDE=CVS:.svn\fR
.SH "SEE ALSO"
.IX Header "SEE ALSO"
.IP "\fI/usr/share/doc/debhelper/examples/\fR" 4
.IX Item "/usr/share/doc/debhelper/examples/"
A set of example \fIdebian/rules\fR files that use debhelper.
.IP "<http://joeyh.name/code/debhelper/>" 4
.IX Item "<http://joeyh.name/code/debhelper/>"
Debhelper web site.
.SH "AUTHOR"
.IX Header "AUTHOR"
Joey Hess <joeyh@debian.org>