1 This file documents things you should know to write a new debhelper program.
2 Any program with a name that begins with dh_ should conform to these
3 guidelines (with the historical exception of dh_make).
8 There are lots of debhelper commands. To make the learning curve shallower,
9 I want them all to behave in a standard manner:
11 All debhelper programs have names beginning with "dh_". This is so we don't
12 pollute the name space too much.
14 Debhelper programs should never output anything to standard output except
15 error messages, important warnings, and the actual commands they run that
16 modify files under debian/ (this last only if they are passed -v, and if you
17 output the commands, you should indent them with 1 tab). This is so we don't
18 have a lot of noise output when all the debhelper commands in a debian/rules
19 are run, so the important stuff is clearly visible.
21 Debhelper programs should accept all options listed in the "SHARED
22 DEBHELPER OPTIONS" section of debhelper(7), including any long forms of
23 these options, like --verbose . If necessary, the options may be ignored.
25 If debhelper commands need config files, they should use
26 debian/package.filename as the name of the config file (replace filename
27 with whatever your command wants), and debian/filename should also be
28 checked for config information for the first binary package in
29 debian/control. Also, debhelper commands should accept the same sort of
30 information that appears in the config files, on their command lines, if
31 possible, and apply that information to the first package they act on.
32 The config file format should be as simple as possible, generally just a
33 list of files to act on.
35 Debhelper programs should never modify the debian/postinst, debian/prerm,
36 etc scripts. Instead, they can add lines to debian/postinst.debhelper, etc.
37 The autoscript() function (see below) is one easy way to do this.
38 dh_installdeb is an exception, it will run after the other commands and
39 merge these modifications into the actual postinst scripts.
41 In general, files named debian/*.debhelper are internal to debhelper, and
42 their existence or use should not be relied on by external programs such as
43 the build process of a package. These files will be deleted by dh_clean.
45 Debhelper programs should default to doing exactly what policy says to do.
47 There are always exceptions. Just ask me.
49 Introducing Dh_Lib.pm:
52 Dh_Lib.pm is the library used by all debhelper programs to parse their
53 arguments and set some useful variables. It's not mandatory that your
54 program use Dh_Lib.pm, but it will make it a lot easier to keep it in sync
55 with the rest of debhelper if it does, so this is highly encouraged.
57 (There used to be a version of Dh_lib.pm that was a library of functions for
58 shell scripts. If you want to write a debhelper command that is a shell
59 script, I can dig up that old library for you. Only the perl one is
60 supported now, though.)
62 Use Dh_Lib.pm like this:
64 use Debian::Debhelper::Dh_Lib
67 The BEGIN block is there to make perl look for the module in all the right
70 The init() function causes Dh_lib to parse the command line and do some other
76 All debhelper programs should respond to certain arguments, such as -v, -i,
77 -a, and -p. To help you make this work right, Dh_Lib.pm handles argument
78 processing. Just call init().
80 After argument processing, some global variables are used to hold the
81 results; programs can use them later. These variables are elements of the
84 switch variable description
85 -v VERBOSE should the program verbosely output what it is
87 --no-act NO_ACT should the program not actually do anything?
88 -i,-a,-p,-N DOPACKAGES a space delimited list of the binary packages
89 to act on (in Dh_Lib.pm, this is an array)
90 -i DOINDEP set if we're acting on binary independent
92 -a DOARCH set if we're acting on binary dependent
94 -n NOSCRIPTS if set, do not make any modifications to the
95 package's postinst, postrm, etc scripts.
96 -o ONLYSCRIPTS if set, only make modifications to the
97 package's scripts, but don't look for or
98 install associated files.
99 -X EXCLUDE exclude a something from processing (you
100 decide what this means for your program)
102 EXCLUDE_FIND same as DH_EXCLUDE, except all items are put
103 into a string in a way that they will make
104 find find them. (Use ! in front to negate
107 include conffiles. It's -x for obscure
109 -d D_FLAG you decide what this means to your program
110 -r R_FLAG you decide what this means to your program
111 -k K_FLAG you decide what this means to your program
112 -P TMPDIR package build directory (implies only one
113 package is being acted on)
114 -u U_PARAMS will be set to a string, that is typically
115 parameters your program passes on to some
116 other program. (This is an array)
117 -m M_PARAMS will be set to a string, you decide what it
118 means to your program
119 -l L_PARAMS will be set to a string, you decide what it
120 means to your program
121 -V V_FLAG will be set to a string, you decide what it
122 means to your program
123 -V V_FLAG_SET will be 1 if -V was specified, even if no
124 parameters were passed along with the -V
125 -A PARAMS_ALL generally means that additional command line
126 parameters passed to the program (other than
127 those processed here), will apply to all
128 binary packages the program acts on, not just
130 --init-script INIT_SCRIPT will be set to a string, which specifies an
131 init script name (probably only
132 dh_installinit will ever use this)
133 --sourcedir SOURCEDIR will be set to a string (probably only
134 dh_movefiles will ever use this)
135 --destdir DESTDIR will be set to a string (probably only
136 dh_builddeb will ever use this)
137 --filename FILENAME will be set to a string
138 --flavor FLAVOR will be set to a string (probably only
139 dh_installemacsen will ever use this)
140 --number PRIORITY will be set to a number (deprecated)
141 --priority PRIORITY will be set to a number
142 --name NAME a name to use for installed files, instead of
144 --error-handler ERROR_HANDLER a function to call on error
146 Any additional command line parameters that do not start with "-" will be
147 ignored, and you can access them later just as you normally would.
149 If you need a new command line option, just ask me, and I will add it.
154 The following keys are also set in the %dh hash when you call init():
156 MAINPACKAGE the name of the first binary package listed in
158 FIRSTPACKAGE the first package we were instructed to act on. This package
159 typically gets special treatment; additional arguments
160 specified on the command line may effect it.
165 Dh_Lib.pm also contains a number of functions you may find useful.
168 Pass this function an array that is a
169 shell command. It will run the command (unless $dh{NO_ACT} is set), and
170 if $dh{VERBOSE} is set, it will also output the command to stdout. You
171 should use this function for almost all commands your program performs
172 that manipulate files in the package build directories.
173 complex_doit($command)
174 Pass this function a string that is a shell command, it will run it
175 similarly to how doit() does. You can pass more complicated commands
176 to this (ie, commands involving piping redirection), however, you
177 have to worry about things like escaping shell metacharacters.
178 verbose_print($message)
179 Pass this command a string, and it will echo it if $dh{VERBOSE} is set.
181 Pass this command a string, it will output it to standard error and
184 Pass this command a string, and it will output it to standard error
185 as a warning message.
187 Pass this command the name of a binary package, it will return the
188 name of the tmp directory that will be used as this package's
189 package build directory. Typically, this will be "debian/package".
191 Pass this command a number, and if the current compatibility level
192 is less than or equal to that number, it will return true.
193 Looks at DH_COMPAT to get the compatibility level.
194 pkgfile($package, $basename)
195 Pass this command the name of a binary package, and the base name of a
196 file, and it will return the actual filename to use. This is used
197 for allowing debhelper programs to have configuration files in the
198 debian/ directory, so there can be one config file per binary
199 package. The convention is that the files are named
200 debian/package.filename, and debian/filename is also allowable for
201 the $dh{MAINPACKAGE}. If the file does not exist, nothing is returned.
203 Pass this command the name of a binary package, and it will return
204 the name to prefix to files in debian/ for this package. For the
205 $dh{MAINPACKAGE}, it returns nothing (there is no prefix), for the other
206 packages, it returns "package.".
208 Pass this command the name of a package, it returns 1 if the package
209 is a native debian package.
210 As a side effect, $dh{VERSION} is set to the version number of the
212 autoscript($package, $scriptname, $snippetname, $sedcommands)
214 - binary package to be affected
216 - filename of snippet
217 - sed commands to run on the snippet. Ie, s/#PACKAGE#/$PACKAGE/
219 This command automatically adds shell script snippets to a debian
220 maintainer script (like the postinst or prerm).
222 Return directory part of pathname.
224 Return base of pathname,
225 addsubstvar($package, $substvar, $deppackage, $verinfo, $remove)
226 This function adds a dependency on some package to the specified
227 substvar in a package's substvar's file. It needs all these
229 - binary package that gets the item
230 - name of the substvar to add the item to
231 - the package that will be depended on
232 - version info for the package (optional) (ie: ">= 1.1")
233 - if this last parameter is passed, the thing that would be added
234 is removed instead. This can be useful to ensure that a debhelper
235 command is idempotent. Note that without this parameter, if you
236 call the function twice with the same values it will only add one
237 item to the substvars file.
238 delsubstvar($package, $substvar)
239 This function removes the entire line for the substvar from the
240 package's shlibs file.
241 excludefile($filename)
242 This function returns true if -X has been used to ask for the file
245 Returns true if the package is marked as a udeb in the control
247 udeb_filename($package)
248 Returns the filename of the udeb package.
250 Returns a list of packages in the control file.
251 Must pass "arch" or "indep" or "same" to specify arch-dependent or
252 -independent or same arch packages. If nothing is specified, returns all
254 As a side effect, populates %package_arches and %package_types with
255 the types of all packages (not only those returned).
257 -- Joey Hess <joeyh@debian.org>