3 debhelper - the debhelper tool suite
7 B<dh_>I<*> [B<-v>] [B<-a>] [B<-i>] [B<-s>] [B<--no-act>] [B<-ppackage>] [B<-Npackage] [-Ptmpdir>]
11 Debhelper is used to help you build a debian package. The philosophy behind
12 debhelper is to provide a collection of small, simple, and easily
13 understood tools that are used in debian/rules to automate various common
14 aspects of building a package. This means less work for you, the packager.
15 It also, to some degree means that these tools can be changed if debian
16 policy changes, and packages that use them will require only a rebuild to
17 comply with the new policy.
19 A typical debian/rules file that uses debhelper will call several debhelper
20 commands in sequence, or use L<dh(1)> to automate this process. Examples of
21 rules files that use debhelper are in F</usr/share/doc/debhelper/examples/>
23 To create a new debian package using debhelper, you can just copy one of
24 the sample rules files and edit it by hand. Or you can try the dh-make
25 package, which contains a L<dh_make|dh_make(1)> command that partially
26 automates the process. For a more gentle introduction, the maint-guide debian
27 package contains a tutorial about making your first package using debhelper.
29 =head1 DEBHELPER COMMANDS
31 Here is the complete list of available debhelper commands. See their man
32 pages for additional documentation.
40 If a program's name starts with "dh_", and the program is not on the above
41 list, then it is not part of the debhelper package, but it should still
42 work like the other programs described on this page.
44 =head1 DEBHELPER CONFIG FILES
46 Many debhelper commands make use of files in F<debian/> to control what they
47 do. Besides the common F<debian/changelog> and F<debian/control>, which are
48 in all packages, not just those using debhelper, some additional files can
49 be used to configure the behavior of specific debhelper commands. These
50 files are typically named debian/package.foo (where "package" of course,
51 is replaced with the package that is being acted on).
53 For example, dh_installdocs uses files named debian/package.docs to list
54 the documentation files it will install. See the man pages of individual
55 commands for details about the names and formats of the files they use.
56 Generally, these files will list files to act on, one file per line. Some
57 programs in debhelper use pairs of files and destinations or slightly more
60 Note that if a package is the first (or only) binary package listed in
61 debian/control, debhelper will use debian/foo if no debian/package.foo
64 In some rare cases, you may want to have different versions of these files
65 for different architectures or OSes. If files named debian/package.foo.ARCH
66 or debian/package.foo.OS exist, where "ARCH" and "OS" are the same as the
67 output of "dpkg-architecture -qDEB_HOST_ARCH" /
68 "dpkg-architecture -qDEB_HOST_ARCH_OS",
69 then they will be used in preference to other, more general files.
71 In many cases, these config files are used to specify various types of
72 files. Documentation or example files to install, files to move, and so on.
73 When appropriate, in cases like these, you can use standard shell wildcard
74 characters ('?' and '*' and '[..]' character classes) in the files.
76 You can also put comments in these files; lines beginning with "#" are
79 =head1 SHARED DEBHELPER OPTIONS
81 The following command line options are supported by all debhelper programs.
85 =item B<-v>, B<--verbose>
87 Verbose mode: show all commands that modify the package build directory.
91 Do not really do anything. If used with -v, the result is that the command
92 will output what it would have done.
94 =item B<-a>, B<--arch>
96 Act on all architecture dependent packages.
98 =item B<-i>, B<--indep>
100 Act on all architecture independent packages.
102 =item B<->I<ppackage>, B<--package=>I<package>
104 Act on the package named "package". This option may be specified multiple
105 times to make debhelper operate on a given set of packages.
107 =item B<-s>, B<--same-arch>
109 This is a smarter version of the -a flag, that is used in some rare
110 circumstances. It understands that if the control file lists "Architecture: i386"
111 for the package, the package should not be acted on on other architectures. So
112 this flag makes the command act on all "Architecture: any" packages, as well
113 as on any packages that have the current architecture explicitly specified.
114 Contrast to the -a flag, which makes the command work on all packages that
115 are not architecture independent.
117 =item B<-N>I<package>, B<--no-package=>I<package>
119 Do not act on the specified package even if an -a, -i, or -p option lists
120 the package as one that should be acted on.
122 =item B<--remaining-packages>
124 Do not act on the packages which have already been acted on by this debhelper
125 command earlier (i.e. if the command is present in the package debhelper log).
126 For example, if you need to call the command with special options only for a
127 couple of binary packages, pass this option to the last call of the command to
128 process the rest of packages with default settings.
130 =item B<--ignore=>I<file>
132 Ignore the specified file. This can be used if debian/ contains a debhelper
133 config file that a debhelper command should not act on. Note that
134 debian/compat, debian/control, and debian/changelog can't be ignored, but
135 then, there should never be a reason to ignore those files.
137 For example, if upstream ships a debian/init that you don't want
138 dh_installinit to install, use --ignore=debian/init
140 =item B<-P>I<tmpdir>, B<--tmpdir=>I<tmpdir>
142 Use "tmpdir" for package build directory. The default is debian/<package>
144 =item B<--mainpackage=>I<package>
146 This little-used option changes the package which debhelper considers the
147 "main package", that is, the first one listed in debian/control, and the
148 one for which debian/foo files can be used instead of the usual
149 debian/package.foo files.
153 =head1 COMMON DEBHELPER OPTIONS
155 The following command line options are supported by some debhelper programs.
156 See the man page of each program for a complete explanation of what each
163 Do not modify postinst/postrm/etc scripts.
165 =item B<-X>I<item>, B<--exclude=>I<item>
167 Exclude an item from processing. This option may be used multiple times,
168 to exclude more than one thing.
170 =item B<-A>, B<--all>
172 Makes files or other items that are specified on the command line take effect
173 in ALL packages acted on, not just the first.
179 =head2 Multiple binary package support
181 If your source package generates more than one binary package, debhelper
182 programs will default to acting on all binary packages when run. If your
183 source package happens to generate one architecture dependent package, and
184 another architecture independent package, this is not the correct behavior,
185 because you need to generate the architecture dependent packages in the
186 binary-arch debian/rules target, and the architecture independent packages
187 in the binary-indep debian/rules target.
189 To facilitate this, as well as give you more control over which packages
190 are acted on by debhelper programs, all debhelper programs accept the
191 B<-a>, B<-i>, B<-p>, and B<-s> parameters. These parameters are cumulative.
192 If none are given, debhelper programs default to acting on all packages listed
195 =head2 Automatic generation of debian install scripts
197 Some debhelper commands will automatically generate parts of debian
198 maintainer scripts. If you want these automatically generated things
199 included in your existing debian maintainer scripts, then you need to add
200 "#DEBHELPER#" to your scripts, in the place the code should be added.
201 "#DEBHELPER#" will be replaced by any auto-generated code when you run
204 If a script does not exist at all and debhelper needs to add something to
205 it, then debhelper will create the complete script.
207 All debhelper commands that automatically generate code in this way let it
208 be disabled by the -n parameter (see above).
210 Note that the inserted code will be shell code, so you cannot directly use
211 it in a perl script. If you would like to embed it into a perl script, here
212 is one way to do that (note that I made sure that $1, $2, etc are set with
215 my $temp="set -e\nset -- @ARGV\n" . << 'EOF';
218 system ($temp) / 256 == 0
219 or die "Problem with debhelper scripts: $!";
221 =head2 Automatic generation of miscellaneous dependencies.
223 Some debhelper commands may make the generated package need to depend on
224 some other packages. For example, if you use L<dh_installdebconf(1)>, your
225 package will generally need to depend on debconf. Or if you use
226 L<dh_installxfonts(1)>, your package will generally need to depend on a
227 particular version of xutils. Keeping track of these miscellaneous
228 dependencies can be annoying since they are dependant on how debhelper does
229 things, so debhelper offers a way to automate it.
231 All commands of this type, besides documenting what dependencies may be
232 needed on their man pages, will automatically generate a substvar called
233 ${misc:Depends}. If you put that token into your debian/control file, it
234 will be expanded to the dependencies debhelper figures you need.
236 This is entirely independent of the standard ${shlibs:Depends} generated by
237 L<dh_makeshlibs(1)>, and the ${perl:Depends} generated by L<dh_perl(1)>.
238 You can choose not to use any of these, if debhelper's guesses don't match
241 =head2 Package build directories
243 By default, all debhelper programs assume that the temporary directory used
244 for assembling the tree of files in a package is debian/<package>.
246 Sometimes, you might want to use some other temporary directory. This is
247 supported by the -P flag. For example, "dh_installdocs -Pdebian/tmp", will
248 use debian/tmp as the temporary directory. Note that if you use -P, the
249 debhelper programs can only be acting on a single package at a time. So if
250 you have a package that builds many binary packages, you will need to also
251 use the -p flag to specify which binary package the debhelper program will
254 =head2 Debhelper compatibility levels
256 From time to time, major non-backwards-compatible changes need to be made
257 to debhelper, to keep it clean and well-designed as needs change and its
258 author gains more experience. To prevent such major changes from breaking
259 existing packages, the concept of debhelper compatibility levels was
260 introduced. You tell debhelper which compatibility level it should use, and
261 it modifies its behavior in various ways.
263 Tell debhelper what compatibility level to use by writing a number to
264 debian/compat. For example, to turn on V7 mode:
266 % echo 7 > debian/compat
268 Unless otherwise indicated, all debhelper documentation assumes that you
269 are using the most recent compatibility level, and in most cases does not
270 indicate if the behavior is different in an earlier compatibility level, so
271 if you are not using the most recent compatibility level, you're advised to
272 read below for notes about what is different in earlier compatibility
275 These are the available compatibility levels:
281 This is the original debhelper compatibility level, and so it is the default
282 one. In this mode, debhelper will use debian/tmp as the package tree
283 directory for the first binary package listed in the control file, while using
284 debian/<package> for all other packages listed in the control file.
286 This mode is deprecated.
290 In this mode, debhelper will consistently use debian/<package>
291 as the package tree directory for every package that is built.
293 This mode is deprecated.
297 This mode works like V2, with the following additions:
303 Debhelper config files support globbing via * and ?, when appropriate. To
304 turn this off and use those characters raw, just prefix with a backslash.
308 dh_makeshlibs makes the postinst and postrm scripts call ldconfig.
312 Every file in etc/ is automatically flagged as a conffile by dh_installdeb.
316 This mode is deprecated.
326 dh_makeshlibs -V will not include the debian part of the version number in
327 the generated dependency line in the shlibs file.
331 You are encouraged to put the new ${misc:Depends} into debian/control to
332 supplement the ${shlibs:Depends} field.
336 dh_fixperms will make all files in bin/ directories and in etc/init.d
341 dh_link will correct existing links to conform with policy.
345 This mode is deprecated.
355 Comments are ignored in debhelper config files.
359 dh_strip --dbg-package now specifies the name of a package to put debugging
360 symbols in, not the packages to take the symbols from.
364 dh_installdocs skips installing empty files.
368 dh_install errors out if wildcards expand to nothing.
380 Commands that generate maintainer script fragments will order the
381 fragments in reverse order for the prerm and postrm scripts.
385 dh_installwm will install a slave manpage link for x-window-manager.1.gz,
386 if it sees the man page in usr/share/man/man1 in the package build
391 dh_builddeb did not previously delete everything matching
392 DH_ALWAYS_EXCLUDE, if it was set to a list of things to exclude, such as
393 "CVS:.svn:.git". Now it does.
397 dh_installman allows overwriting existing man pages in the package build
398 directory. In previous compatibility levels it silently refuses to do this.
404 This is the recommended mode of operation.
412 dh_install, will fall back to looking for files in debian/tmp if it doesn't
413 find them in the current directory (or wherever you tell it look using
414 --sourcedir). This allows dh_install to interoperate with dh_auto_install,
415 which installs to debian/tmp, without needing any special parameters.
419 dh_clean will read debian/clean and delete files listed there.
423 dh_clean will delete toplevel *-stamp files.
427 dh_installchangelogs will guess at what file is the upstream changelog if
434 =head2 Doc directory symlinks
436 Sometimes it is useful to make a package not contain a /usr/share/doc/package
437 directory at all, instead placing just a dangling symlink in the binary
438 package, that points to some other doc directory. Policy says this is ok if
439 your package depends on the package whose doc directory it uses. To
440 accomplish this, just don't tell debhelper to install any documentation
441 files into the package, and use dh_link to set up the symlink (or do it by
442 hand), and debhelper should do the right thing: notice it is a dangling
443 symlink and not try to install a copyright file or changelog.
447 Debhelper includes support for udebs. To create a udeb with debhelper,
448 add "XC-Package-Type: udeb" to the package's stanza in debian/control, and
449 build-depend on debhelper (>= 4.2). Debhelper will try to create udebs that
450 comply with debian-installer policy, by making the generated package files
451 end in ".udeb", not installing any documentation into a udeb, skipping over
452 preinst, postrm, prerm, and config scripts, etc.
456 In general, if any debhelper program needs a directory to exist under
457 debian/, it will create it. I haven't bothered to document this in all the
458 man pages, but for example, dh_installdeb knows to make debian/<package>/DEBIAN/
459 before trying to put files there, dh_installmenu knows you need a
460 debian/<package>/usr/share/menu/ before installing the menu files, etc.
462 Once your package uses debhelper to build, be sure to add
463 debhelper to your Build-Depends line in debian/control. You should
464 build-depend on a version of debhelper equal to (or greater than) the
465 debhelper compatibility level your package uses. So if your package used
466 compatibility level 7:
468 Build-Depends: debhelper (>= 7)
476 Set to 1 to enable verbose mode. Debhelper will output every command it runs
477 that modifies files on the build system.
481 Temporarily specifies what compatibility level debhelper should run at,
482 overriding any value in debian/compat.
486 Set to 1 to enable no-act mode.
490 Anything in this variable will be prepended to the command line arguments
491 of all debhelper commands. Command-specific options will be ignored by
492 commands that do not support them.
494 This is useful in some situations, for example, if you need to pass -p to
495 all debhelper commands that will be run. One good way to set DH_OPTIONS is
496 by using "Target-specific Variable Values" in your debian/rules file. See
497 the make documentation for details on doing this.
499 =item DH_ALWAYS_EXCLUDE
501 If set, this adds the value the variable is set to to the -X options of all
502 commands that support the -X option. Moreover, dh_builddeb will rm -rf
503 anything that matches the value in your package build tree.
505 This can be useful if you are doing a build from a CVS source tree, in
506 which case setting DH_ALWAYS_EXCLUDE=CVS will prevent any CVS directories
507 from sneaking into the package you build. Or, if a package has a source
508 tarball that (unwisely) includes CVS directories, you might want to export
509 DH_ALWAYS_EXCLUDE=CVS in debian/rules, to make it take effect wherever
510 your package is built.
512 Multiple things to exclude can be separated with colons, as in
513 DH_ALWAYS_EXCLUDE=CVS:.svn
521 =item F</usr/share/doc/debhelper/examples/>
523 A set of example debian/rules files that use debhelper.
525 =item L<http://kitenet.net/~joey/code/debhelper/>
533 Joey Hess <joeyh@debian.org>