.\" Automatically generated by Pod::Man 4.10 (Pod::Simple 3.35) .\" .\" 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 >0, 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 "DH_INSTALLDEB 1" .TH DH_INSTALLDEB 1 "2021-03-06" "13.3.3~bpo10+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" dh_installdeb \- install files into the DEBIAN directory .SH "SYNOPSIS" .IX Header "SYNOPSIS" \&\fBdh_installdeb\fR [\fIdebhelperĀ options\fR] .SH "DESCRIPTION" .IX Header "DESCRIPTION" \&\fBdh_installdeb\fR is a debhelper program that is responsible for installing files into the \fI\s-1DEBIAN\s0\fR directories in package build directories with the correct permissions. .SH "FILES" .IX Header "FILES" .IP "\fIpackage\fR.postinst" 4 .IX Item "package.postinst" .PD 0 .IP "\fIpackage\fR.preinst" 4 .IX Item "package.preinst" .IP "\fIpackage\fR.postrm" 4 .IX Item "package.postrm" .IP "\fIpackage\fR.prerm" 4 .IX Item "package.prerm" .PD These maintainer scripts are installed into the \fI\s-1DEBIAN\s0\fR directory. .Sp \&\fBdh_installdeb\fR will perform substitution of known tokens of the pattern \fB#TOKEN#\fR. In generally, scripts will want to include the \fB#DEBHELPER#\fR to benefit from the shell scripts generated by debhelper commands (including those from \&\fBdh_installdeb\fR when it processes \fIpackage\fR.maintscript files). .Sp The \fB#DEBHELPER#\fR token should be placed on its own line as it is often replaced by a multi-line shell script. .IP "\fIpackage\fR.triggers" 4 .IX Item "package.triggers" .PD 0 .IP "\fIpackage\fR.shlibs" 4 .IX Item "package.shlibs" .PD These control files are installed into the \fI\s-1DEBIAN\s0\fR directory. .Sp Note that \fIpackage\fR.shlibs is only installed in compat level 9 and earlier. In compat 10, please use \fBdh_makeshlibs\fR\|(1). .IP "\fIpackage\fR.conffiles" 4 .IX Item "package.conffiles" Historically, this file was needed to manually mark files files as conffiles. However, it has become de facto obsolete since debhelper automatically computed which files should be marked as conffiles. .Sp In compatibility level up and including 11, this control file will be installed into the \fI\s-1DEBIAN\s0\fR directory. In compatibility level 12 and later, the file is silently ignored. .IP "\fIpackage\fR.maintscript" 4 .IX Item "package.maintscript" Lines in this file correspond to \fBdpkg\-maintscript\-helper\fR\|(1) commands and parameters. However, the \*(L"maint-script-parameters\*(R" should \fInot\fR be included as debhelper will add those automatically. .Sp Example: .Sp .Vb 4 \& # Correct \& rm_conffile /etc/obsolete.conf 0.2~ foo \& # INCORRECT \& rm_conffile /etc/obsolete.conf 0.2~ foo \-\- "$@" .Ve .Sp In compat 10 or later, any shell metacharacters will be escaped, so arbitrary shell code cannot be inserted here. For example, a line such as \f(CW\*(C`mv_conffile /etc/oldconffile /etc/newconffile\*(C'\fR will insert maintainer script snippets into all maintainer scripts sufficient to move that conffile. .Sp It was also the intention to escape shell metacharacters in previous compat levels. However, it did not work properly and as such it was possible to embed arbitrary shell code in earlier compat levels. .Sp The \fBdh_installdeb\fR tool will do some basic validation of some of the commands listed in this file to catch common mistakes. The validation is enabled as a warning since compat 10 and as a hard error in compat 12. .Sp Supports substitution variables in compat 13 and later as documented in \fBdebhelper\fR\|(7). .SH "OPTIONS" .IX Header "OPTIONS" .IP "\fB\-D\fR\fITOKEN=VALUE\fR, \fB\-\-define\fR \fITOKEN=VALUE\fR" 4 .IX Item "-DTOKEN=VALUE, --define TOKEN=VALUE" Define tokens to be replaced inside the maintainer scripts when it is generated. Please note that the limitations described in \&\*(L"Limitations in token names\*(R" also applies to tokens defined on the command line. Invalid token names will trigger an error. .Sp In the simple case, this parameter will cause \fB#\f(BI\s-1TOKEN\s0\fB#\fR to be replaced by \fI\s-1VALUE\s0\fR. If \fI\s-1VALUE\s0\fR starts with a literal \&\fI@\fR\-sign, then \fI\s-1VALUE\s0\fR is expected to point to a file containing the actual value to insert. .Sp An explicit declared token with this parameter will replace built-in tokens. .Sp Test examples to aid with the understanding: .Sp .Vb 6 \& cat >> debian/postinst < some\-file \& dh_installdeb \-\-define SIMPLE=direct \-\-define FILEBASED=@some\-file .Ve .Sp In this example, \fB#SIMPLE#\fR will expand to \fBdirect\fR and \fB#FILEBASED#\fR will expand to \fBComplex value\fR. .Sp It is also possible to set package-specific values for a given token. This is useful when \fBdh_installdeb\fR is acting on multiple packages that need different values for the same token. This is done by prefixing the token name with \fBpkg.\f(BIpackage-name\fB.\fR. .Sp This can be used as in the following example: .Sp .Vb 10 \& cat >> debian/foo.postinst <> debian/bar.postinst <> debian/baz.postinst <