1 <!doctype debiandoc system [
2 <!-- include version information so we don't have to hard code it
3 within the document -->
4 <!entity % versiondata SYSTEM "version.ent"> %versiondata;
10 <title>Debian Policy Manual</title>
11 <author><qref id="authors">The Debian Policy Mailing List</qref></author>
12 <version>version &version;, &date;</version>
15 This manual describes the policy requirements for the Debian
16 GNU/Linux distribution. This includes the structure and
17 contents of the Debian archive and several design issues of
18 the operating system, as well as technical requirements that
19 each package must satisfy to be included in the distribution.
24 Copyright © 1996,1997,1998 Ian Jackson
25 and Christian Schwarz.
28 This manual is free software; you may redistribute it and/or
29 modify it under the terms of the GNU General Public License
30 as published by the Free Software Foundation; either version
31 2, or (at your option) any later version.
35 This is distributed in the hope that it will be useful, but
36 <em>without any warranty</em>; without even the implied
37 warranty of merchantability or fitness for a particular
38 purpose. See the GNU General Public License for more
43 A copy of the GNU General Public License is available as
44 <file>/usr/share/common-licenses/GPL</file> in the Debian GNU/Linux
45 distribution or on the World Wide Web at
46 <url id="http://www.gnu.org/copyleft/gpl.html"
47 name="the GNU General Public Licence">. You can also
48 obtain it by writing to the Free Software Foundation, Inc.,
49 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
57 <heading>About this manual</heading>
59 <heading>Scope</heading>
61 This manual describes the policy requirements for the Debian
62 GNU/Linux distribution. This includes the structure and
63 contents of the Debian archive and several design issues of the
64 operating system, as well as technical requirements that
65 each package must satisfy to be included in the
70 This manual also describes Debian policy as it relates to
71 creating Debian packages. It is not a tutorial on how to build
72 packages, nor is it exhaustive where it comes to describing
73 the behavior of the packaging system. Instead, this manual
74 attempts to define the interface to the package management
75 system that the developers have to be conversant with.<footnote>
76 Informally, the criteria used for inclusion is that the
77 material meet one of the following requirements:
78 <taglist compact="compact">
79 <tag>Standard interfaces</tag>
81 The material presented represents an interface to
82 the packaging system that is mandated for use, and
83 is used by, a significant number of packages, and
84 therefore should not be changed without peer
85 review. Package maintainers can then rely on this
86 interfaces not changing, and the package
87 management software authors need to ensure
88 compatibility with these interface
89 definitions. (Control file and changelog file
90 formats are examples.)
92 <tag>Chosen Convention</tag>
94 If there are a number of technically viable choices
95 that can be made, but one needs to select one of
96 these options for inter-operability. The version
97 number format is one example.
100 Please note that these are not mutually exclusive;
101 selected conventions often become parts of standard
107 The footnotes present in this manual are
108 merely informative, and are not part of Debian policy itself.
112 The appendices to this manual are not necessarily normative,
113 either. Please see <ref id="pkg-scope"> for more information.
117 In the normative part of this manual,
118 the words <em>must</em>, <em>should</em> and
119 <em>may</em>, and the adjectives <em>required</em>,
120 <em>recommended</em> and <em>optional</em>, are used to
121 distinguish the significance of the various guidelines in
122 this policy document. Packages that do not conform to the
123 guidelines denoted by <em>must</em> (or <em>required</em>)
124 will generally not be considered acceptable for the Debian
125 distribution. Non-conformance with guidelines denoted by
126 <em>should</em> (or <em>recommended</em>) will generally be
127 considered a bug, but will not necessarily render a package
128 unsuitable for distribution. Guidelines denoted by
129 <em>may</em> (or <em>optional</em>) are truly optional and
130 adherence is left to the maintainer's discretion.
134 These classifications are roughly equivalent to the bug
135 severities <em>serious</em> (for <em>must</em> or
136 <em>required</em> directive violations), <em>minor</em>,
137 <em>normal</em> or <em>important</em>
138 (for <em>should</em> or <em>recommended</em> directive
139 violations) and <em>wishlist</em> (for <em>optional</em>
142 Compare RFC 2119. Note, however, that these words are
143 used in a different way in this document.
148 Much of the information presented in this manual will be
149 useful even when building a package which is to be
150 distributed in some other way or is intended for local use
156 <heading>New versions of this document</heading>
159 This manual is distributed via the Debian package
160 <package><url name="debian-policy"
161 id="http://packages.debian.org/debian-policy"></package>
162 (<httpsite>packages.debian.org</httpsite>
163 <httppath>/debian-policy</httppath>).
167 The current version of this document is also available from
168 the Debian web mirrors at
169 <tt><url name="/doc/debian-policy/"
170 id="http://www.debian.org/doc/debian-policy/"></tt>.
172 <httpsite>www.debian.org</httpsite>
173 <httppath>/doc/debian-policy/</httppath>)
174 Also available from the same directory are several other
175 formats: <file>policy.html.tar.gz</file>
176 (<httppath>/doc/debian-policy/policy.html.tar.gz</httppath>),
177 <file>policy.pdf.gz</file>
178 (<httppath>/doc/debian-policy/policy.pdf.gz</httppath>)
179 and <file>policy.ps.gz</file>
180 (<httppath>/doc/debian-policy/policy.ps.gz</httppath>).
184 The <package>debian-policy</package> package also includes the file
185 <file>upgrading-checklist.txt.gz</file> which indicates policy
186 changes between versions of this document.
191 <heading>Authors and Maintainers</heading>
194 Originally called "Debian GNU/Linux Policy Manual", this
195 manual was initially written in 1996 by Ian Jackson.
196 It was revised on November 27th, 1996 by David A. Morris.
197 Christian Schwarz added new sections on March 15th, 1997,
198 and reworked/restructured it in April-July 1997.
199 Christoph Lameter contributed the "Web Standard".
200 Julian Gilbey largely restructured it in 2001.
204 Since September 1998, the responsibility for the contents of
205 this document lies on the <url name="debian-policy mailing list"
206 id="mailto:debian-policy@lists.debian.org">. Proposals
207 are discussed there and inserted into policy after a certain
208 consensus is established.
209 <!-- insert shameless policy-process plug here eventually -->
210 The actual editing is done by a group of maintainers that have
211 no editorial powers. These are the current maintainers:
214 <item>Julian Gilbey</item>
215 <item>Branden Robinson</item>
216 <item>Josip Rodin</item>
217 <item>Manoj Srivastava</item>
222 While the authors of this document have tried hard to avoid
223 typos and other errors, these do still occur. If you discover
224 an error in this manual or if you want to give any
225 comments, suggestions, or criticisms please send an email to
226 the Debian Policy List,
227 <email>debian-policy@lists.debian.org</email>, or submit a
228 bug report against the <tt>debian-policy</tt> package.
232 Please do not try to reach the individual authors or maintainers
233 of the Policy Manual regarding changes to the Policy.
238 <heading>Related documents</heading>
241 There are several other documents other than this Policy Manual
242 that are necessary to fully understand some Debian policies and
247 The external "sub-policy" documents are referred to in:
248 <list compact="compact">
249 <item><ref id="fhs"></item>
250 <item><ref id="virtual_pkg"></item>
251 <item><ref id="menus"></item>
252 <item><ref id="mime"></item>
253 <item><ref id="perl"></item>
254 <item><ref id="maintscriptprompt"></item>
255 <item><ref id="emacs"></item>
260 In addition to those, which carry the weight of policy, there
261 is the Debian Developer's Reference. This document describes
262 procedures and resources for Debian developers, but it is
263 <em>not</em> normative; rather, it includes things that don't
264 belong in the Policy, such as best practices for developers.
268 The Developer's Reference is available in the
269 <package>developers-reference</package> package.
270 It's also available from the Debian web mirrors at
271 <tt><url name="/doc/developers-reference/"
272 id="http://www.debian.org/doc/developers-reference/"></tt>.
276 <sect id="definitions">
277 <heading>Definitions</heading>
280 The following terms are used in this Policy Manual:
284 The character encoding specified by ANSI X3.4-1986 and its
285 predecessor standards, referred to in MIME as US-ASCII, and
286 corresponding to an encoding in eight bits per character of
287 the first 128 <url id="http://www.unicode.org/"
288 name="Unicode"> characters, with the eighth bit always zero.
292 The transformation format (sometimes called encoding) of
293 <url id="http://www.unicode.org/" name="Unicode"> defined by
294 <url id="http://www.rfc-editor.org/rfc/rfc3629.txt"
295 name="RFC 3629">. UTF-8 has the useful property of having
296 ASCII as a subset, so any text encoded in ASCII is trivially
306 <heading>The Debian Archive</heading>
309 The Debian GNU/Linux system is maintained and distributed as a
310 collection of <em>packages</em>. Since there are so many of
311 them (currently well over 15000), they are split into
312 <em>sections</em> and given <em>priorities</em> to simplify
313 the handling of them.
317 The effort of the Debian project is to build a free operating
318 system, but not every package we want to make accessible is
319 <em>free</em> in our sense (see the Debian Free Software
320 Guidelines, below), or may be imported/exported without
321 restrictions. Thus, the archive is split into areas<footnote>
322 The Debian archive software uses the term "component" internally
323 and in the Release file format to refer to the division of an
324 archive. The Debian Social Contract simply refers to "areas."
325 This document uses terminology similar to the Social Contract.
326 </footnote> based on their licenses and other restrictions.
330 The aims of this are:
332 <list compact="compact">
333 <item>to allow us to make as much software available as we can</item>
334 <item>to allow us to encourage everyone to write free software,
336 <item>to allow us to make it easy for people to produce
337 CD-ROMs of our system without violating any licenses,
338 import/export restrictions, or any other laws.</item>
343 The <em>main</em> archive area forms the <em>Debian GNU/Linux
348 Packages in the other archive areas (<tt>contrib</tt>,
349 <tt>non-free</tt>) are not considered to be part of the Debian
350 distribution, although we support their use and provide
351 infrastructure for them (such as our bug-tracking system and
352 mailing lists). This Debian Policy Manual applies to these
357 <heading>The Debian Free Software Guidelines</heading>
359 The Debian Free Software Guidelines (DFSG) form our
360 definition of "free software". These are:
362 <tag>Free Redistribution
365 The license of a Debian component may not restrict any
366 party from selling or giving away the software as a
367 component of an aggregate software distribution
368 containing programs from several different
369 sources. The license may not require a royalty or
370 other fee for such sale.
375 The program must include source code, and must allow
376 distribution in source code as well as compiled form.
381 The license must allow modifications and derived
382 works, and must allow them to be distributed under the
383 same terms as the license of the original software.
385 <tag>Integrity of The Author's Source Code
388 The license may restrict source-code from being
389 distributed in modified form <em>only</em> if the
390 license allows the distribution of "patch files"
391 with the source code for the purpose of modifying the
392 program at build time. The license must explicitly
393 permit distribution of software built from modified
394 source code. The license may require derived works to
395 carry a different name or version number from the
396 original software. (This is a compromise. The Debian
397 Project encourages all authors to not restrict any
398 files, source or binary, from being modified.)
400 <tag>No Discrimination Against Persons or Groups
403 The license must not discriminate against any person
406 <tag>No Discrimination Against Fields of Endeavor
409 The license must not restrict anyone from making use
410 of the program in a specific field of endeavor. For
411 example, it may not restrict the program from being
412 used in a business, or from being used for genetic
415 <tag>Distribution of License
418 The rights attached to the program must apply to all
419 to whom the program is redistributed without the need
420 for execution of an additional license by those
423 <tag>License Must Not Be Specific to Debian
426 The rights attached to the program must not depend on
427 the program's being part of a Debian system. If the
428 program is extracted from Debian and used or
429 distributed without Debian but otherwise within the
430 terms of the program's license, all parties to whom
431 the program is redistributed must have the same
432 rights as those that are granted in conjunction with
435 <tag>License Must Not Contaminate Other Software
438 The license must not place restrictions on other
439 software that is distributed along with the licensed
440 software. For example, the license must not insist
441 that all other programs distributed on the same medium
442 must be free software.
444 <tag>Example Licenses
447 The "GPL," "BSD," and "Artistic" licenses are examples of
448 licenses that we consider <em>free</em>.
455 <heading>Archive areas</heading>
458 <heading>The main archive area</heading>
461 Every package in <em>main</em> must comply with the DFSG
462 (Debian Free Software Guidelines).
466 In addition, the packages in <em>main</em>
467 <list compact="compact">
469 must not require a package outside of <em>main</em>
470 for compilation or execution (thus, the package must
471 not declare a "Depends", "Recommends", or
472 "Build-Depends" relationship on a non-<em>main</em>
476 must not be so buggy that we refuse to support them,
480 must meet all policy requirements presented in this
489 <heading>The contrib archive area</heading>
492 Every package in <em>contrib</em> must comply with the DFSG.
496 In addition, the packages in <em>contrib</em>
497 <list compact="compact">
499 must not be so buggy that we refuse to support them,
503 must meet all policy requirements presented in this
511 Examples of packages which would be included in
512 <em>contrib</em> are:
513 <list compact="compact">
515 free packages which require <em>contrib</em>,
516 <em>non-free</em> packages or packages which are not
517 in our archive at all for compilation or execution,
521 wrapper packages or other sorts of free accessories for
528 <sect1 id="non-free">
529 <heading>The non-free archive area</heading>
532 Packages must be placed in <em>non-free</em> if they are
533 not compliant with the DFSG or are encumbered by patents
534 or other legal issues that make their distribution
539 In addition, the packages in <em>non-free</em>
540 <list compact="compact">
542 must not be so buggy that we refuse to support them,
546 must meet all policy requirements presented in this
547 manual that it is possible for them to meet.
549 It is possible that there are policy
550 requirements which the package is unable to
551 meet, for example, if the source is
552 unavailable. These situations will need to be
553 handled on a case-by-case basis.
562 <sect id="pkgcopyright">
563 <heading>Copyright considerations</heading>
566 Every package must be accompanied by a verbatim copy of
567 its copyright and distribution license in the file
568 <file>/usr/share/doc/<var>package</var>/copyright</file>
569 (see <ref id="copyrightfile"> for further details).
573 We reserve the right to restrict files from being included
574 anywhere in our archives if
575 <list compact="compact">
577 their use or distribution would break a law,
580 there is an ethical conflict in their distribution or
584 we would have to sign a license for them, or
587 their distribution would conflict with other project
594 Programs whose authors encourage the user to make
595 donations are fine for the main distribution, provided
596 that the authors do not claim that not donating is
597 immoral, unethical, illegal or something similar; in such
598 a case they must go in <em>non-free</em>.
602 Packages whose copyright permission notices (or patent
603 problems) do not even allow redistribution of binaries
604 only, and where no special permission has been obtained,
605 must not be placed on the Debian FTP site and its mirrors
610 Note that under international copyright law (this applies
611 in the United States, too), <em>no</em> distribution or
612 modification of a work is allowed without an explicit
613 notice saying so. Therefore a program without a copyright
614 notice <em>is</em> copyrighted and you may not do anything
615 to it without risking being sued! Likewise if a program
616 has a copyright notice but no statement saying what is
617 permitted then nothing is permitted.
621 Many authors are unaware of the problems that restrictive
622 copyrights (or lack of copyright notices) can cause for
623 the users of their supposedly-free software. It is often
624 worthwhile contacting such authors diplomatically to ask
625 them to modify their license terms. However, this can be a
626 politically difficult thing to do and you should ask for
627 advice on the <tt>debian-legal</tt> mailing list first, as
632 When in doubt about a copyright, send mail to
633 <email>debian-legal@lists.debian.org</email>. Be prepared
634 to provide us with the copyright statement. Software
635 covered by the GPL, public domain software and BSD-like
636 copyrights are safe; be wary of the phrases "commercial
637 use prohibited" and "distribution restricted".
641 <sect id="subsections">
642 <heading>Sections</heading>
645 The packages in the archive areas <em>main</em>,
646 <em>contrib</em> and <em>non-free</em> are grouped further into
647 <em>sections</em> to simplify handling.
651 The archive area and section for each package should be
652 specified in the package's <tt>Section</tt> control record (see
653 <ref id="f-Section">). However, the maintainer of the Debian
654 archive may override this selection to ensure the consistency of
655 the Debian distribution. The <tt>Section</tt> field should be
657 <list compact="compact">
659 <em>section</em> if the package is in the
660 <em>main</em> archive area,
663 <em>area/section</em> if the package is in
664 the <em>contrib</em> or <em>non-free</em>
671 The Debian archive maintainers provide the authoritative
672 list of sections. At present, they are:
673 <em>admin</em>, <em>cli-mono</em>, <em>comm</em>, <em>database</em>,
674 <em>devel</em>, <em>debug</em>, <em>doc</em>, <em>editors</em>,
675 <em>electronics</em>, <em>embedded</em>, <em>fonts</em>,
676 <em>games</em>, <em>gnome</em>, <em>graphics</em>, <em>gnu-r</em>,
677 <em>gnustep</em>, <em>hamradio</em>, <em>haskell</em>,
678 <em>httpd</em>, <em>interpreters</em>, <em>java</em>, <em>kde</em>,
679 <em>kernel</em>, <em>libs</em>, <em>libdevel</em>, <em>lisp</em>,
680 <em>localization</em>, <em>mail</em>, <em>math</em>, <em>misc</em>,
681 <em>net</em>, <em>news</em>, <em>ocaml</em>, <em>oldlibs</em>,
682 <em>otherosfs</em>, <em>perl</em>, <em>php</em>, <em>python</em>,
683 <em>ruby</em>, <em>science</em>, <em>shells</em>, <em>sound</em>,
684 <em>tex</em>, <em>text</em>, <em>utils</em>, <em>vcs</em>,
685 <em>video</em>, <em>web</em>, <em>x11</em>, <em>xfce</em>,
690 <sect id="priorities">
691 <heading>Priorities</heading>
694 Each package should have a <em>priority</em> value, which is
695 included in the package's <em>control record</em>
696 (see <ref id="f-Priority">).
697 This information is used by the Debian package management tools to
698 separate high-priority packages from less-important packages.
702 The following <em>priority levels</em> are recognized by the
703 Debian package management tools.
705 <tag><tt>required</tt></tag>
707 Packages which are necessary for the proper
708 functioning of the system (usually, this means that
709 dpkg functionality depends on these packages).
710 Removing a <tt>required</tt> package may cause your
711 system to become totally broken and you may not even
712 be able to use <prgn>dpkg</prgn> to put things back,
713 so only do so if you know what you are doing. Systems
714 with only the <tt>required</tt> packages are probably
715 unusable, but they do have enough functionality to
716 allow the sysadmin to boot and install more software.
718 <tag><tt>important</tt></tag>
720 Important programs, including those which one would
721 expect to find on any Unix-like system. If the
722 expectation is that an experienced Unix person who
723 found it missing would say "What on earth is going on,
724 where is <prgn>foo</prgn>?", it must be an
725 <tt>important</tt> package.<footnote>
726 This is an important criterion because we are
727 trying to produce, amongst other things, a free
730 Other packages without which the system will not run
731 well or be usable must also have priority
732 <tt>important</tt>. This does
733 <em>not</em> include Emacs, the X Window System, TeX
734 or any other large applications. The
735 <tt>important</tt> packages are just a bare minimum of
736 commonly-expected and necessary tools.
738 <tag><tt>standard</tt></tag>
740 These packages provide a reasonably small but not too
741 limited character-mode system. This is what will be
742 installed by default if the user doesn't select anything
743 else. It doesn't include many large applications.
745 <tag><tt>optional</tt></tag>
747 (In a sense everything that isn't required is
748 optional, but that's not what is meant here.) This is
749 all the software that you might reasonably want to
750 install if you didn't know what it was and don't have
751 specialized requirements. This is a much larger system
752 and includes the X Window System, a full TeX
753 distribution, and many applications. Note that
754 optional packages should not conflict with each other.
756 <tag><tt>extra</tt></tag>
758 This contains all packages that conflict with others
759 with required, important, standard or optional
760 priorities, or are only likely to be useful if you
761 already know what they are or have specialized
762 requirements (such as packages containing only detached
769 Packages must not depend on packages with lower priority
770 values (excluding build-time dependencies). In order to
771 ensure this, the priorities of one or more packages may need
780 <heading>Binary packages</heading>
783 The Debian GNU/Linux distribution is based on the Debian
784 package management system, called <prgn>dpkg</prgn>. Thus,
785 all packages in the Debian distribution must be provided
786 in the <tt>.deb</tt> file format.
790 <heading>The package name</heading>
793 Every package must have a name that's unique within the Debian
798 The package name is included in the control field
799 <tt>Package</tt>, the format of which is described
800 in <ref id="f-Package">.
801 The package name is also included as a part of the file name
802 of the <tt>.deb</tt> file.
807 <heading>The version of a package</heading>
810 Every package has a version number recorded in its
811 <tt>Version</tt> control file field, described in
812 <ref id="f-Version">.
816 The package management system imposes an ordering on version
817 numbers, so that it can tell whether packages are being up- or
818 downgraded and so that package system front end applications
819 can tell whether a package it finds available is newer than
820 the one installed on the system. The version number format
821 has the most significant parts (as far as comparison is
822 concerned) at the beginning.
826 If an upstream package has problematic version numbers they
827 should be converted to a sane form for use in the
828 <tt>Version</tt> field.
832 <heading>Version numbers based on dates</heading>
835 In general, Debian packages should use the same version
836 numbers as the upstream sources.
840 However, in some cases where the upstream version number is
841 based on a date (e.g., a development "snapshot" release) the
842 package management system cannot handle these version
843 numbers without epochs. For example, dpkg will consider
844 "96May01" to be greater than "96Dec24".
848 To prevent having to use epochs for every new upstream
849 version, the date based portion of the version number
850 should be changed to the following format in such cases:
851 "19960501", "19961224". It is up to the maintainer whether
852 they want to bother the upstream maintainer to change
853 the version numbers upstream, too.
857 Note that other version formats based on dates which are
858 parsed correctly by the package management system should
859 <em>not</em> be changed.
863 Native Debian packages (i.e., packages which have been
864 written especially for Debian) whose version numbers include
865 dates should always use the "YYYYMMDD" format.
872 <heading>The maintainer of a package</heading>
875 Every package must have a Debian maintainer (the
876 maintainer may be one person or a group of people
877 reachable from a common email address, such as a mailing
878 list). The maintainer is responsible for ensuring that
879 the package is placed in the appropriate distributions.
883 The maintainer must be specified in the
884 <tt>Maintainer</tt> control field with their correct name
885 and a working email address. If one person maintains
886 several packages, they should try to avoid having
887 different forms of their name and email address in
888 the <tt>Maintainer</tt> fields of those packages.
892 The format of the <tt>Maintainer</tt> control field is
893 described in <ref id="f-Maintainer">.
897 If the maintainer of a package quits from the Debian
898 project, "Debian QA Group"
899 <email>packages@qa.debian.org</email> takes over the
900 maintainer-ship of the package until someone else
901 volunteers for that task. These packages are called
902 <em>orphaned packages</em>.<footnote>
903 The detailed procedure for doing this gracefully can
904 be found in the Debian Developer's Reference,
905 see <ref id="related">.
910 <sect id="descriptions">
911 <heading>The description of a package</heading>
914 Every Debian package must have an extended description
915 stored in the appropriate field of the control record.
916 The technical information about the format of the
917 <tt>Description</tt> field is in <ref id="f-Description">.
921 The description should describe the package (the program) to a
922 user (system administrator) who has never met it before so that
923 they have enough information to decide whether they want to
924 install it. This description should not just be copied verbatim
925 from the program's documentation.
929 Put important information first, both in the synopsis and
930 extended description. Sometimes only the first part of the
931 synopsis or of the description will be displayed. You can
932 assume that there will usually be a way to see the whole
933 extended description.
937 The description should also give information about the
938 significant dependencies and conflicts between this package
939 and others, so that the user knows why these dependencies and
940 conflicts have been declared.
944 Instructions for configuring or using the package should
945 not be included (that is what installation scripts,
946 manual pages, info files, etc., are for). Copyright
947 statements and other administrivia should not be included
948 either (that is what the copyright file is for).
951 <sect1 id="synopsis"><heading>The single line synopsis</heading>
954 The single line synopsis should be kept brief - certainly
959 Do not include the package name in the synopsis line. The
960 display software knows how to display this already, and you
961 do not need to state it. Remember that in many situations
962 the user may only see the synopsis line - make it as
963 informative as you can.
968 <sect1 id="extendeddesc"><heading>The extended description</heading>
971 Do not try to continue the single line synopsis into the
972 extended description. This will not work correctly when
973 the full description is displayed, and makes no sense
974 where only the summary (the single line synopsis) is
979 The extended description should describe what the package
980 does and how it relates to the rest of the system (in terms
981 of, for example, which subsystem it is which part of).
985 The description field needs to make sense to anyone, even
986 people who have no idea about any of the things the
987 package deals with.<footnote>
988 The blurb that comes with a program in its
989 announcements and/or <prgn>README</prgn> files is
990 rarely suitable for use in a description. It is
991 usually aimed at people who are already in the
992 community where the package is used.
1001 <heading>Dependencies</heading>
1004 Every package must specify the dependency information
1005 about other packages that are required for the first to
1010 For example, a dependency entry must be provided for any
1011 shared libraries required by a dynamically-linked executable
1012 binary in a package.
1016 Packages are not required to declare any dependencies they
1017 have on other packages which are marked <tt>Essential</tt>
1018 (see below), and should not do so unless they depend on a
1019 particular version of that package.<footnote>
1021 Essential is needed in part to avoid unresolvable dependency
1022 loops on upgrade. If packages add unnecessary dependencies
1023 on packages in this set, the chances that there
1024 <strong>will</strong> be an unresolvable dependency loop
1025 caused by forcing these Essential packages to be configured
1026 first before they need to be is greatly increased. It also
1027 increases the chances that frontends will be unable to
1028 <strong>calculate</strong> an upgrade path, even if one
1032 Also, functionality is rarely ever removed from the
1033 Essential set, but <em>packages</em> have been removed from
1034 the Essential set when the functionality moved to a
1035 different package. So depending on these packages <em>just
1036 in case</em> they stop being essential does way more harm
1043 Sometimes, a package requires another package to be installed
1044 <em>and</em> configured before it can be installed. In this
1045 case, you must specify a <tt>Pre-Depends</tt> entry for
1050 You should not specify a <tt>Pre-Depends</tt> entry for a
1051 package before this has been discussed on the
1052 <tt>debian-devel</tt> mailing list and a consensus about
1053 doing that has been reached.
1057 The format of the package interrelationship control fields is
1058 described in <ref id="relationships">.
1062 <sect id="virtual_pkg">
1063 <heading>Virtual packages</heading>
1066 Sometimes, there are several packages which offer
1067 more-or-less the same functionality. In this case, it's
1068 useful to define a <em>virtual package</em> whose name
1069 describes that common functionality. (The virtual
1070 packages only exist logically, not physically; that's why
1071 they are called <em>virtual</em>.) The packages with this
1072 particular function will then <em>provide</em> the virtual
1073 package. Thus, any other package requiring that function
1074 can simply depend on the virtual package without having to
1075 specify all possible packages individually.
1079 All packages should use virtual package names where
1080 appropriate, and arrange to create new ones if necessary.
1081 They should not use virtual package names (except privately,
1082 amongst a cooperating group of packages) unless they have
1083 been agreed upon and appear in the list of virtual package
1084 names. (See also <ref id="virtual">)
1088 The latest version of the authoritative list of virtual
1089 package names can be found in the <tt>debian-policy</tt> package.
1090 It is also available from the Debian web mirrors at
1091 <tt><url name="/doc/packaging-manuals/virtual-package-names-list.txt"
1092 id="http://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt"></tt>.
1096 The procedure for updating the list is described in the preface
1103 <heading>Base system</heading>
1106 The <tt>base system</tt> is a minimum subset of the Debian
1107 GNU/Linux system that is installed before everything else
1108 on a new system. Only very few packages are allowed to form
1109 part of the base system, in order to keep the required disk
1114 The base system consists of all those packages with priority
1115 <tt>required</tt> or <tt>important</tt>. Many of them will
1116 be tagged <tt>essential</tt> (see below).
1121 <heading>Essential packages</heading>
1124 Essential is defined as the minimal set of functionality that
1125 must be available and usable on the system at all times, even
1126 when packages are in an unconfigured (but unpacked) state.
1127 Packages are tagged <tt>essential</tt> for a system using the
1128 <tt>Essential</tt> control file field. The format of the
1129 <tt>Essential</tt> control field is described in <ref
1134 Since these packages cannot be easily removed (one has to
1135 specify an extra <em>force option</em> to
1136 <prgn>dpkg</prgn> to do so), this flag must not be used
1137 unless absolutely necessary. A shared library package
1138 must not be tagged <tt>essential</tt>; dependencies will
1139 prevent its premature removal, and we need to be able to
1140 remove it when it has been superseded.
1144 Since dpkg will not prevent upgrading of other packages
1145 while an <tt>essential</tt> package is in an unconfigured
1146 state, all <tt>essential</tt> packages must supply all of
1147 their core functionality even when unconfigured. If the
1148 package cannot satisfy this requirement it must not be
1149 tagged as essential, and any packages depending on this
1150 package must instead have explicit dependency fields as
1155 Maintainers should take great care in adding any programs,
1156 interfaces, or functionality to <tt>essential</tt> packages.
1157 Packages may assume that functionality provided by
1158 <tt>essential</tt> packages is always available without
1159 declaring explicit dependencies, which means that removing
1160 functionality from the Essential set is very difficult and is
1161 almost never done. Any capability added to an
1162 <tt>essential</tt> package therefore creates an obligation to
1163 support that capability as part of the Essential set in
1168 You must not tag any packages <tt>essential</tt> before
1169 this has been discussed on the <tt>debian-devel</tt>
1170 mailing list and a consensus about doing that has been
1175 <sect id="maintscripts">
1176 <heading>Maintainer Scripts</heading>
1179 The package installation scripts should avoid producing
1180 output which is unnecessary for the user to see and
1181 should rely on <prgn>dpkg</prgn> to stave off boredom on
1182 the part of a user installing many packages. This means,
1183 amongst other things, using the <tt>--quiet</tt> option on
1184 <prgn>install-info</prgn>.
1188 Errors which occur during the execution of an installation
1189 script must be checked and the installation must not
1190 continue after an error.
1194 Note that in general <ref id="scripts"> applies to package
1195 maintainer scripts, too.
1199 You should not use <prgn>dpkg-divert</prgn> on a file
1200 belonging to another package without consulting the
1201 maintainer of that package first.
1205 All packages which supply an instance of a common command
1206 name (or, in general, filename) should generally use
1207 <prgn>update-alternatives</prgn>, so that they may be
1208 installed together. If <prgn>update-alternatives</prgn>
1209 is not used, then each package must use
1210 <tt>Conflicts</tt> to ensure that other packages are
1211 de-installed. (In this case, it may be appropriate to
1212 specify a conflict against earlier versions of something
1213 that previously did not use
1214 <prgn>update-alternatives</prgn>; this is an exception to
1215 the usual rule that versioned conflicts should be
1219 <sect1 id="maintscriptprompt">
1220 <heading>Prompting in maintainer scripts</heading>
1222 Package maintainer scripts may prompt the user if
1223 necessary. Prompting must be done by communicating
1224 through a program, such as <prgn>debconf</prgn>, which
1225 conforms to the Debian Configuration Management
1226 Specification, version 2 or higher.
1230 Packages which are essential, or which are dependencies of
1231 essential packages, may fall back on another prompting method
1232 if no such interface is available when they are executed.
1236 The Debian Configuration Management Specification is included
1237 in the <file>debconf_specification</file> files in the
1238 <package>debian-policy</package> package.
1239 It is also available from the Debian web mirrors at
1240 <tt><url name="/doc/packaging-manuals/debconf_specification.html"
1241 id="http://www.debian.org/doc/packaging-manuals/debconf_specification.html"></tt>.
1245 Packages which use the Debian Configuration Management
1246 Specification may contain an additional
1247 <prgn>config</prgn> script and a <tt>templates</tt>
1248 file in their control archive<footnote>
1249 The control.tar.gz inside the .deb.
1250 See <manref name="deb" section="5">.
1252 The <prgn>config</prgn> script might be run before the
1253 <prgn>preinst</prgn> script, and before the package is unpacked
1254 or any of its dependencies or pre-dependencies are satisfied.
1255 Therefore it must work using only the tools present in
1256 <em>essential</em> packages.<footnote>
1257 <package>Debconf</package> or another tool that
1258 implements the Debian Configuration Management
1259 Specification will also be installed, and any
1260 versioned dependencies on it will be satisfied
1261 before preconfiguration begins.
1266 Packages which use the Debian Configuration Management
1267 Specification must allow for translation of their user-visible
1268 messages by using a gettext-based system such as the one
1269 provided by the <package>po-debconf</package> package.
1273 Packages should try to minimize the amount of prompting
1274 they need to do, and they should ensure that the user
1275 will only ever be asked each question once. This means
1276 that packages should try to use appropriate shared
1277 configuration files (such as <file>/etc/papersize</file> and
1278 <file>/etc/news/server</file>), and shared
1279 <package>debconf</package> variables rather than each
1280 prompting for their own list of required pieces of
1285 It also means that an upgrade should not ask the same
1286 questions again, unless the user has used
1287 <tt>dpkg --purge</tt> to remove the package's configuration.
1288 The answers to configuration questions should be stored in an
1289 appropriate place in <file>/etc</file> so that the user can
1290 modify them, and how this has been done should be
1295 If a package has a vitally important piece of
1296 information to pass to the user (such as "don't run me
1297 as I am, you must edit the following configuration files
1298 first or you risk your system emitting badly-formatted
1299 messages"), it should display this in the
1300 <prgn>config</prgn> or <prgn>postinst</prgn> script and
1301 prompt the user to hit return to acknowledge the
1302 message. Copyright messages do not count as vitally
1303 important (they belong in
1304 <file>/usr/share/doc/<var>package</var>/copyright</file>);
1305 neither do instructions on how to use a program (these
1306 should be in on-line documentation, where all the users
1311 Any necessary prompting should almost always be confined
1312 to the <prgn>config</prgn> or <prgn>postinst</prgn>
1313 script. If it is done in the <prgn>postinst</prgn>, it
1314 should be protected with a conditional so that
1315 unnecessary prompting doesn't happen if a package's
1316 installation fails and the <prgn>postinst</prgn> is
1317 called with <tt>abort-upgrade</tt>,
1318 <tt>abort-remove</tt> or <tt>abort-deconfigure</tt>.
1328 <heading>Source packages</heading>
1330 <sect id="standardsversion">
1331 <heading>Standards conformance</heading>
1334 Source packages should specify the most recent version number
1335 of this policy document with which your package complied
1336 when it was last updated.
1340 This information may be used to file bug reports
1341 automatically if your package becomes too much out of date.
1345 The version is specified in the <tt>Standards-Version</tt>
1347 The format of the <tt>Standards-Version</tt> field is
1348 described in <ref id="f-Standards-Version">.
1352 You should regularly, and especially if your package has
1353 become out of date, check for the newest Policy Manual
1354 available and update your package, if necessary. When your
1355 package complies with the new standards you should update the
1356 <tt>Standards-Version</tt> source package field and
1357 release it.<footnote>
1358 See the file <file>upgrading-checklist</file> for
1359 information about policy which has changed between
1360 different versions of this document.
1366 <sect id="pkg-relations">
1367 <heading>Package relationships</heading>
1370 Source packages should specify which binary packages they
1371 require to be installed or not to be installed in order to
1372 build correctly. For example, if building a package
1373 requires a certain compiler, then the compiler should be
1374 specified as a build-time dependency.
1378 It is not necessary to explicitly specify build-time
1379 relationships on a minimal set of packages that are always
1380 needed to compile, link and put in a Debian package a
1381 standard "Hello World!" program written in C or C++. The
1382 required packages are called <em>build-essential</em>, and
1383 an informational list can be found in
1384 <file>/usr/share/doc/build-essential/list</file> (which is
1385 contained in the <tt>build-essential</tt>
1388 <list compact="compact">
1390 This allows maintaining the list separately
1391 from the policy documents (the list does not
1392 need the kind of control that the policy
1396 Having a separate package allows one to install
1397 the build-essential packages on a machine, as
1398 well as allowing other packages such as tasks to
1399 require installation of the build-essential
1400 packages using the depends relation.
1403 The separate package allows bug reports against
1404 the list to be categorized separately from
1405 the policy management process in the BTS.
1412 When specifying the set of build-time dependencies, one
1413 should list only those packages explicitly required by the
1414 build. It is not necessary to list packages which are
1415 required merely because some other package in the list of
1416 build-time dependencies depends on them.<footnote>
1417 The reason for this is that dependencies change, and
1418 you should list all those packages, and <em>only</em>
1419 those packages that <em>you</em> need directly. What
1420 others need is their business. For example, if you
1421 only link against <file>libimlib</file>, you will need to
1422 build-depend on <package>libimlib2-dev</package> but
1423 not against any <tt>libjpeg*</tt> packages, even
1424 though <tt>libimlib2-dev</tt> currently depends on
1425 them: installation of <package>libimlib2-dev</package>
1426 will automatically ensure that all of its run-time
1427 dependencies are satisfied.
1432 If build-time dependencies are specified, it must be
1433 possible to build the package and produce working binaries
1434 on a system with only essential and build-essential
1435 packages installed and also those required to satisfy the
1436 build-time relationships (including any implied
1437 relationships). In particular, this means that version
1438 clauses should be used rigorously in build-time
1439 relationships so that one cannot produce bad or
1440 inconsistently configured packages when the relationships
1441 are properly satisfied.
1445 <ref id="relationships"> explains the technical details.
1450 <heading>Changes to the upstream sources</heading>
1453 If changes to the source code are made that are not
1454 specific to the needs of the Debian system, they should be
1455 sent to the upstream authors in whatever form they prefer
1456 so as to be included in the upstream version of the
1461 If you need to configure the package differently for
1462 Debian or for Linux, and the upstream source doesn't
1463 provide a way to do so, you should add such configuration
1464 facilities (for example, a new <prgn>autoconf</prgn> test
1465 or <tt>#define</tt>) and send the patch to the upstream
1466 authors, with the default set to the way they originally
1467 had it. You can then easily override the default in your
1468 <file>debian/rules</file> or wherever is appropriate.
1472 You should make sure that the <prgn>configure</prgn> utility
1473 detects the correct architecture specification string
1474 (refer to <ref id="arch-spec"> for details).
1478 If you need to edit a <prgn>Makefile</prgn> where GNU-style
1479 <prgn>configure</prgn> scripts are used, you should edit the
1480 <file>.in</file> files rather than editing the
1481 <prgn>Makefile</prgn> directly. This allows the user to
1482 reconfigure the package if necessary. You should
1483 <em>not</em> configure the package and edit the generated
1484 <prgn>Makefile</prgn>! This makes it impossible for someone
1485 else to later reconfigure the package without losing the
1491 <sect id="dpkgchangelog">
1492 <heading>Debian changelog: <file>debian/changelog</file></heading>
1495 Changes in the Debian version of the package should be
1496 briefly explained in the Debian changelog file
1497 <file>debian/changelog</file>.<footnote>
1499 Mistakes in changelogs are usually best rectified by
1500 making a new changelog entry rather than "rewriting
1501 history" by editing old changelog entries.
1504 This includes modifications
1505 made in the Debian package compared to the upstream one
1506 as well as other changes and updates to the package.
1508 Although there is nothing stopping an author who is also
1509 the Debian maintainer from using this changelog for all
1510 their changes, it will have to be renamed if the Debian
1511 and upstream maintainers become different people. In such
1512 a case, however, it might be better to maintain the package
1513 as a non-native package.
1518 The format of the <file>debian/changelog</file> allows the
1519 package building tools to discover which version of the package
1520 is being built and find out other release-specific information.
1524 That format is a series of entries like this:
1526 <example compact="compact">
1527 <var>package</var> (<var>version</var>) <var>distribution(s)</var>; urgency=<var>urgency</var>
1529 [optional blank line(s), stripped]
1531 * <var>change details</var>
1532 <var>more change details</var>
1534 [blank line(s), included in output of dpkg-parsechangelog]
1536 * <var>even more change details</var>
1538 [optional blank line(s), stripped]
1540 -- <var>maintainer name</var> <<var>email address</var>><var>[two spaces]</var> <var>date</var>
1545 <var>package</var> and <var>version</var> are the source
1546 package name and version number.
1550 <var>distribution(s)</var> lists the distributions where
1551 this version should be installed when it is uploaded - it
1552 is copied to the <tt>Distribution</tt> field in the
1553 <file>.changes</file> file. See <ref id="f-Distribution">.
1557 <var>urgency</var> is the value for the <tt>Urgency</tt>
1558 field in the <file>.changes</file> file for the upload
1559 (see <ref id="f-Urgency">). It is not possible to specify
1560 an urgency containing commas; commas are used to separate
1561 <tt><var>keyword</var>=<var>value</var></tt> settings in the
1562 <prgn>dpkg</prgn> changelog format (though there is
1563 currently only one useful <var>keyword</var>,
1568 The change details may in fact be any series of lines
1569 starting with at least two spaces, but conventionally each
1570 change starts with an asterisk and a separating space and
1571 continuation lines are indented so as to bring them in
1572 line with the start of the text above. Blank lines may be
1573 used here to separate groups of changes, if desired.
1577 If this upload resolves bugs recorded in the Bug Tracking
1578 System (BTS), they may be automatically closed on the
1579 inclusion of this package into the Debian archive by
1580 including the string: <tt>closes: Bug#<var>nnnnn</var></tt>
1581 in the change details.<footnote>
1582 To be precise, the string should match the following
1583 Perl regular expression:
1585 /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i
1587 Then all of the bug numbers listed will be closed by the
1588 archive maintenance script (<prgn>katie</prgn>) using the
1589 <var>version</var> of the changelog entry.
1591 This information is conveyed via the <tt>Closes</tt> field
1592 in the <tt>.changes</tt> file (see <ref id="f-Closes">).
1596 The maintainer name and email address used in the changelog
1597 should be the details of the person uploading <em>this</em>
1598 version. They are <em>not</em> necessarily those of the
1599 usual package maintainer. The information here will be
1600 copied to the <tt>Changed-By</tt> field in the
1601 <tt>.changes</tt> file (see <ref id="f-Changed-By">),
1602 and then later used to send an acknowledgement when the
1603 upload has been installed.
1607 The <var>date</var> must be in RFC822 format<footnote>
1608 This is generated by <tt>date -R</tt>.
1609 </footnote>; it must include the time zone specified
1610 numerically, with the time zone name or abbreviation
1611 optionally present as a comment in parentheses.
1615 The first "title" line with the package name must start
1616 at the left hand margin. The "trailer" line with the
1617 maintainer and date details must be preceded by exactly
1618 one space. The maintainer details and the date must be
1619 separated by exactly two spaces.
1623 The entire changelog must be encoded in UTF-8.
1627 For more information on placement of the changelog files
1628 within binary packages, please see <ref id="changelogs">.
1632 <sect id="dpkgcopyright">
1633 <heading>Copyright: <file>debian/copyright</file></heading>
1635 Every package must be accompanied by a verbatim copy of
1636 its copyright and distribution license in the file
1637 <file>/usr/share/doc/<var>package</var>/copyright</file>
1638 (see <ref id="copyrightfile"> for further details). Also see
1639 <ref id="pkgcopyright"> for further considerations relayed
1640 to copyrights for packages.
1644 <heading>Error trapping in makefiles</heading>
1647 When <prgn>make</prgn> invokes a command in a makefile
1648 (including your package's upstream makefiles and
1649 <file>debian/rules</file>), it does so using <prgn>sh</prgn>. This
1650 means that <prgn>sh</prgn>'s usual bad error handling
1651 properties apply: if you include a miniature script as one
1652 of the commands in your makefile you'll find that if you
1653 don't do anything about it then errors are not detected
1654 and <prgn>make</prgn> will blithely continue after
1659 Every time you put more than one shell command (this
1660 includes using a loop) in a makefile command you
1661 must make sure that errors are trapped. For
1662 simple compound commands, such as changing directory and
1663 then running a program, using <tt>&&</tt> rather
1664 than semicolon as a command separator is sufficient. For
1665 more complex commands including most loops and
1666 conditionals you should include a separate <tt>set -e</tt>
1667 command at the start of every makefile command that's
1668 actually one of these miniature shell scripts.
1672 <sect id="timestamps">
1673 <heading>Time Stamps</heading>
1675 Maintainers should preserve the modification times of the
1676 upstream source files in a package, as far as is reasonably
1678 The rationale is that there is some information conveyed
1679 by knowing the age of the file, for example, you could
1680 recognize that some documentation is very old by looking
1681 at the modification time, so it would be nice if the
1682 modification time of the upstream source would be
1688 <sect id="restrictions">
1689 <heading>Restrictions on objects in source packages</heading>
1692 The source package may not contain any hard links<footnote>
1694 This is not currently detected when building source
1695 packages, but only when extracting
1699 Hard links may be permitted at some point in the
1700 future, but would require a fair amount of
1703 </footnote>, device special files, sockets or setuid or
1704 setgid files.<footnote>
1705 Setgid directories are allowed.
1710 <sect id="debianrules">
1711 <heading>Main building script: <file>debian/rules</file></heading>
1714 This file must be an executable makefile, and contains the
1715 package-specific recipes for compiling the package and
1716 building binary package(s) from the source.
1720 It must start with the line <tt>#!/usr/bin/make -f</tt>,
1721 so that it can be invoked by saying its name rather than
1722 invoking <prgn>make</prgn> explicitly.
1726 Since an interactive <file>debian/rules</file> script makes it
1727 impossible to auto-compile that package and also makes it
1728 hard for other people to reproduce the same binary
1729 package, all <em>required targets</em> MUST be
1730 non-interactive. At a minimum, required targets are the
1731 ones called by <prgn>dpkg-buildpackage</prgn>, namely,
1732 <em>clean</em>, <em>binary</em>, <em>binary-arch</em>,
1733 <em>binary-indep</em>, and <em>build</em>. It also follows
1734 that any target that these targets depend on must also be
1739 The targets are as follows (required unless stated otherwise):
1741 <tag><tt>build</tt></tag>
1744 The <tt>build</tt> target should perform all the
1745 configuration and compilation of the package.
1746 If a package has an interactive pre-build
1747 configuration routine, the Debianized source package
1748 must either be built after this has taken place (so
1749 that the binary package can be built without rerunning
1750 the configuration) or the configuration routine
1751 modified to become non-interactive. (The latter is
1752 preferable if there are architecture-specific features
1753 detected by the configuration routine.)
1757 For some packages, notably ones where the same
1758 source tree is compiled in different ways to produce
1759 two binary packages, the <tt>build</tt> target
1760 does not make much sense. For these packages it is
1761 good enough to provide two (or more) targets
1762 (<tt>build-a</tt> and <tt>build-b</tt> or whatever)
1763 for each of the ways of building the package, and a
1764 <tt>build</tt> target that does nothing. The
1765 <tt>binary</tt> target will have to build the
1766 package in each of the possible ways and make the
1767 binary package out of each.
1771 The <tt>build</tt> target must not do anything
1772 that might require root privilege.
1776 The <tt>build</tt> target may need to run the
1777 <tt>clean</tt> target first - see below.
1781 When a package has a configuration and build routine
1782 which takes a long time, or when the makefiles are
1783 poorly designed, or when <tt>build</tt> needs to
1784 run <tt>clean</tt> first, it is a good idea to
1785 <tt>touch build</tt> when the build process is
1786 complete. This will ensure that if <tt>debian/rules
1787 build</tt> is run again it will not rebuild the whole
1789 Another common way to do this is for <tt>build</tt>
1790 to depend on <prgn>build-stamp</prgn> and to do
1791 nothing else, and for the <prgn>build-stamp</prgn>
1792 target to do the building and to <tt>touch
1793 build-stamp</tt> on completion. This is
1794 especially useful if the build routine creates a
1795 file or directory called <tt>build</tt>; in such a
1796 case, <tt>build</tt> will need to be listed as
1797 a phony target (i.e., as a dependency of the
1798 <tt>.PHONY</tt> target). See the documentation of
1799 <prgn>make</prgn> for more information on phony
1805 <tag><tt>build-arch</tt> (optional),
1806 <tt>build-indep</tt> (optional)
1810 A package may also provide both of the targets
1811 <tt>build-arch</tt> and <tt>build-indep</tt>.
1812 The <tt>build-arch</tt> target, if provided, should
1813 perform all the configuration and compilation required
1814 for producing all architecture-dependant binary packages
1815 (those packages for which the body of the
1816 <tt>Architecture</tt> field in <tt>debian/control</tt>
1817 is not <tt>all</tt>).
1818 Similarly, the <tt>build-indep</tt> target, if
1819 provided, should perform all the configuration and
1820 compilation required for producing all
1821 architecture-independent binary packages
1822 (those packages for which the body of the
1823 <tt>Architecture</tt> field in <tt>debian/control</tt>
1825 The <tt>build</tt> target should depend on those of the
1826 targets <tt>build-arch</tt> and <tt>build-indep</tt> that
1827 are provided in the rules file.
1831 If one or both of the targets <tt>build-arch</tt> and
1832 <tt>build-indep</tt> are not provided, then invoking
1833 <file>debian/rules</file> with one of the not-provided
1834 targets as arguments should produce a exit status code
1835 of 2. Usually this is provided automatically by make
1836 if the target is missing.
1840 The <tt>build-arch</tt> and <tt>build-indep</tt> targets
1841 must not do anything that might require root privilege.
1845 <tag><tt>binary</tt>, <tt>binary-arch</tt>,
1846 <tt>binary-indep</tt>
1850 The <tt>binary</tt> target must be all that is
1851 necessary for the user to build the binary package(s)
1852 produced from this source package. It is
1853 split into two parts: <prgn>binary-arch</prgn> builds
1854 the binary packages which are specific to a particular
1855 architecture, and <tt>binary-indep</tt> builds
1856 those which are not.
1859 <tt>binary</tt> may be (and commonly is) a target with
1860 no commands which simply depends on
1861 <tt>binary-arch</tt> and <tt>binary-indep</tt>.
1864 Both <tt>binary-*</tt> targets should depend on the
1865 <tt>build</tt> target, or on the appropriate
1866 <tt>build-arch</tt> or <tt>build-indep</tt> target, if
1867 provided, so that the package is built if it has not
1868 been already. It should then create the relevant
1869 binary package(s), using <prgn>dpkg-gencontrol</prgn> to
1870 make their control files and <prgn>dpkg-deb</prgn> to
1871 build them and place them in the parent of the top
1876 Both the <tt>binary-arch</tt> and
1877 <tt>binary-indep</tt> targets <em>must</em> exist.
1878 If one of them has nothing to do (which will always be
1879 the case if the source generates only a single binary
1880 package, whether architecture-dependent or not), it
1881 must still exist and must always succeed.
1885 The <tt>binary</tt> targets must be invoked as
1887 The <prgn>fakeroot</prgn> package often allows one
1888 to build a package correctly even without being
1894 <tag><tt>clean</tt></tag>
1897 This must undo any effects that the <tt>build</tt>
1898 and <tt>binary</tt> targets may have had, except
1899 that it should leave alone any output files created in
1900 the parent directory by a run of a <tt>binary</tt>
1905 If a <tt>build</tt> file is touched at the end of
1906 the <tt>build</tt> target, as suggested above, it
1907 should be removed as the first action that
1908 <tt>clean</tt> performs, so that running
1909 <tt>build</tt> again after an interrupted
1910 <tt>clean</tt> doesn't think that everything is
1915 The <tt>clean</tt> target may need to be
1916 invoked as root if <tt>binary</tt> has been
1917 invoked since the last <tt>clean</tt>, or if
1918 <tt>build</tt> has been invoked as root (since
1919 <tt>build</tt> may create directories, for
1924 <tag><tt>get-orig-source</tt> (optional)</tag>
1927 This target fetches the most recent version of the
1928 original source package from a canonical archive site
1929 (via FTP or WWW, for example), does any necessary
1930 rearrangement to turn it into the original source
1931 tar file format described below, and leaves it in the
1936 This target may be invoked in any directory, and
1937 should take care to clean up any temporary files it
1942 This target is optional, but providing it if
1943 possible is a good idea.
1947 <tag><tt>patch</tt> (optional)</tag>
1950 This target performs whatever additional actions are
1951 required to make the source ready for editing (unpacking
1952 additional upstream archives, applying patches, etc.).
1953 It is recommended to be implemented for any package where
1954 <tt>dpkg-source -x</tt> does not result in source ready
1955 for additional modification. See
1956 <ref id="readmesource">.
1962 The <tt>build</tt>, <tt>binary</tt> and
1963 <tt>clean</tt> targets must be invoked with the current
1964 directory being the package's top-level directory.
1969 Additional targets may exist in <file>debian/rules</file>,
1970 either as published or undocumented interfaces or for the
1971 package's internal use.
1975 The architectures we build on and build for are determined
1976 by <prgn>make</prgn> variables using the utility
1977 <qref id="pkg-dpkg-architecture"><prgn>dpkg-architecture</prgn></qref>.
1978 You can determine the
1979 Debian architecture and the GNU style architecture
1980 specification string for the build machine (the machine type
1981 we are building on) as well as for the host machine (the
1982 machine type we are building for). Here is a list of
1983 supported <prgn>make</prgn> variables:
1984 <list compact="compact">
1986 <tt>DEB_*_ARCH</tt> (the Debian architecture)
1989 <tt>DEB_*_GNU_TYPE</tt> (the GNU style architecture
1990 specification string)
1993 <tt>DEB_*_GNU_CPU</tt> (the CPU part of
1994 <tt>DEB_*_GNU_TYPE</tt>)
1997 <tt>DEB_*_GNU_SYSTEM</tt> (the System part of
1998 <tt>DEB_*_GNU_TYPE</tt>)
2000 where <tt>*</tt> is either <tt>BUILD</tt> for specification of
2001 the build machine or <tt>HOST</tt> for specification of the
2006 Backward compatibility can be provided in the rules file
2007 by setting the needed variables to suitable default
2008 values; please refer to the documentation of
2009 <prgn>dpkg-architecture</prgn> for details.
2013 It is important to understand that the <tt>DEB_*_ARCH</tt>
2014 string only determines which Debian architecture we are
2015 building on or for. It should not be used to get the CPU
2016 or system information; the GNU style variables should be
2020 <sect1 id="debianrules-options">
2021 <heading><file>debian/rules</file> and
2022 <tt>DEB_BUILD_OPTIONS</tt></heading>
2025 Supporting the standardized environment variable
2026 <tt>DEB_BUILD_OPTIONS</tt> is recommended. This variable can
2027 contain several flags to change how a package is compiled and
2028 built. Each flag must be in the form <var>flag</var> or
2029 <var>flag</var>=<var>options</var>. If multiple flags are
2030 given, they must be separated by whitespace.<footnote>
2031 Some packages support any delimiter, but whitespace is the
2032 easiest to parse inside a makefile and avoids ambiguity with
2033 flag values that contain commas.
2035 <var>flag</var> must start with a lowercase letter
2036 (<tt>a-z</tt>) and consist only of lowercase letters,
2037 numbers (<tt>0-9</tt>), and the characters
2038 <tt>-</tt> and <tt>_</tt> (hyphen and underscore).
2039 <var>options</var> must not contain whitespace. The same
2040 tag should not be given multiple times with conflicting
2041 values. Package maintainers may assume that
2042 <tt>DEB_BUILD_OPTIONS</tt> will not contain conflicting tags.
2046 The meaning of the following tags has been standardized:
2050 This tag says to not run any build-time test suite
2051 provided by the package.
2055 The presence of this tag means that the package should
2056 be compiled with a minimum of optimization. For C
2057 programs, it is best to add <tt>-O0</tt> to
2058 <tt>CFLAGS</tt> (although this is usually the default).
2059 Some programs might fail to build or run at this level
2060 of optimization; it may be necessary to use
2061 <tt>-O1</tt>, for example.
2065 This tag means that the debugging symbols should not be
2066 stripped from the binary during installation, so that
2067 debugging information may be included in the package.
2069 <tag>parallel=n</tag>
2071 This tag means that the package should be built using up
2072 to <tt>n</tt> parallel processes if the package build
2073 system supports this.<footnote>
2074 Packages built with <tt>make</tt> can often implement
2075 this by passing the <tt>-j</tt><var>n</var> option to
2078 If the package build system does not support parallel
2079 builds, this string must be ignored. If the package
2080 build system only supports a lower level of concurrency
2081 than <var>n</var>, the package should be built using as
2082 many parallel processes as the package build system
2083 supports. It is up to the package maintainer to decide
2084 whether the package build times are long enough and the
2085 package build system is robust enough to make supporting
2086 parallel builds worthwhile.
2092 Unknown flags must be ignored by <file>debian/rules</file>.
2096 The following makefile snippet is an example of how one may
2097 implement the build options; you will probably have to
2098 massage this example in order to make it work for your
2100 <example compact="compact">
2103 INSTALL_FILE = $(INSTALL) -p -o root -g root -m 644
2104 INSTALL_PROGRAM = $(INSTALL) -p -o root -g root -m 755
2105 INSTALL_SCRIPT = $(INSTALL) -p -o root -g root -m 755
2106 INSTALL_DIR = $(INSTALL) -p -d -o root -g root -m 755
2108 ifneq (,$(filter noopt,$(DEB_BUILD_OPTIONS)))
2113 ifeq (,$(filter nostrip,$(DEB_BUILD_OPTIONS)))
2114 INSTALL_PROGRAM += -s
2116 ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
2117 NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
2118 MAKEFLAGS += -j$(NUMJOBS)
2123 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
2124 # Code to run the package test suite.
2131 <!-- FIXME: section pkg-srcsubstvars is the same as substvars -->
2132 <sect id="substvars">
2133 <heading>Variable substitutions: <file>debian/substvars</file></heading>
2136 When <prgn>dpkg-gencontrol</prgn>,
2137 <prgn>dpkg-genchanges</prgn> and <prgn>dpkg-source</prgn>
2138 generate control files they perform variable substitutions
2139 on their output just before writing it. Variable
2140 substitutions have the form <tt>${<var>variable</var>}</tt>.
2141 The optional file <file>debian/substvars</file> contains
2142 variable substitutions to be used; variables can also be set
2143 directly from <file>debian/rules</file> using the <tt>-V</tt>
2144 option to the source packaging commands, and certain
2145 predefined variables are also available.
2149 The <file>debian/substvars</file> file is usually generated and
2150 modified dynamically by <file>debian/rules</file> targets, in
2151 which case it must be removed by the <tt>clean</tt> target.
2155 See <manref name="deb-substvars" section="5"> for full
2156 details about source variable substitutions, including the
2157 format of <file>debian/substvars</file>.</p>
2160 <sect id="debianwatch">
2161 <heading>Optional upstream source location: <file>debian/watch</file></heading>
2164 This is an optional, recommended control file for the
2165 <tt>uscan</tt> utility which defines how to automatically
2166 scan ftp or http sites for newly available updates of the
2167 package. This is used by <url id="
2168 http://dehs.alioth.debian.org/"> and other Debian QA tools
2169 to help with quality control and maintenance of the
2170 distribution as a whole.
2175 <sect id="debianfiles">
2176 <heading>Generated files list: <file>debian/files</file></heading>
2179 This file is not a permanent part of the source tree; it
2180 is used while building packages to record which files are
2181 being generated. <prgn>dpkg-genchanges</prgn> uses it
2182 when it generates a <file>.changes</file> file.
2186 It should not exist in a shipped source package, and so it
2187 (and any backup files or temporary files such as
2188 <file>files.new</file><footnote>
2189 <file>files.new</file> is used as a temporary file by
2190 <prgn>dpkg-gencontrol</prgn> and
2191 <prgn>dpkg-distaddfile</prgn> - they write a new
2192 version of <tt>files</tt> here before renaming it,
2193 to avoid leaving a corrupted copy if an error
2195 </footnote>) should be removed by the
2196 <tt>clean</tt> target. It may also be wise to
2197 ensure a fresh start by emptying or removing it at the
2198 start of the <tt>binary</tt> target.
2202 When <prgn>dpkg-gencontrol</prgn> is run for a binary
2203 package, it adds an entry to <file>debian/files</file> for the
2204 <file>.deb</file> file that will be created when <tt>dpkg-deb
2205 --build</tt> is run for that binary package. So for most
2206 packages all that needs to be done with this file is to
2207 delete it in the <tt>clean</tt> target.
2211 If a package upload includes files besides the source
2212 package and any binary packages whose control files were
2213 made with <prgn>dpkg-gencontrol</prgn> then they should be
2214 placed in the parent of the package's top-level directory
2215 and <prgn>dpkg-distaddfile</prgn> should be called to add
2216 the file to the list in <file>debian/files</file>.</p>
2219 <sect id="embeddedfiles">
2220 <heading>Convenience copies of code</heading>
2223 Some software packages include in their distribution convenience
2224 copies of code from other software packages, generally so that
2225 users compiling from source don't have to download multiple
2226 packages. Debian packages should not make use of these
2227 convenience copies unless the included package is explicitly
2228 intended to be used in this way.<footnote>
2229 For example, parts of the GNU build system work like this.
2231 If the included code is already in the Debian archive in the
2232 form of a library, the Debian packaging should ensure that
2233 binary packages reference the libraries already in Debian and
2234 the convenience copy is not used. If the included code is not
2235 already in Debian, it should be packaged separately as a
2236 prerequisite if possible.
2238 Having multiple copies of the same code in Debian is
2239 inefficient, often creates either static linking or shared
2240 library conflicts, and, most importantly, increases the
2241 difficulty of handling security vulnerabilities in the
2247 <sect id="readmesource">
2248 <heading>Source package handling:
2249 <file>debian/README.source</file></heading>
2252 If running <prgn>dpkg-source -x</prgn> on a source package
2253 doesn't produce the source of the package, ready for editing,
2254 and allow one to make changes and run
2255 <prgn>dpkg-buildpackage</prgn> to produce a modified package
2256 without taking any additional steps, creating a
2257 <file>debian/README.source</file> documentation file is
2258 recommended. This file should explain how to do all of the
2261 <item>Generate the fully patched source, in a form ready for
2262 editing, that would be built to create Debian
2263 packages. Doing this with a <tt>patch</tt> target in
2264 <file>debian/rules</file> is recommended; see
2265 <ref id="debianrules">.</item>
2266 <item>Modify the source and save those modifications so that
2267 they will be applied when building the package.</item>
2268 <item>Remove source modifications that are currently being
2269 applied when building the package.</item>
2270 <item>Optionally, document what steps are necessary to
2271 upgrade the Debian source package to a new upstream version,
2272 if applicable.</item>
2274 This explanation should include specific commands and mention
2275 any additional required Debian packages. It should not assume
2276 familiarity with any specific Debian packaging system or patch
2281 This explanation may refer to a documentation file installed by
2282 one of the package's build dependencies provided that the
2283 referenced documentation clearly explains these tasks and is not
2284 a general reference manual.
2288 <file>debian/README.source</file> may also include any other
2289 information that would be helpful to someone modifying the
2290 source package. Even if the package doesn't fit the above
2291 description, maintainers are encouraged to document in a
2292 <file>debian/README.source</file> file any source package with a
2293 particularly complex or unintuitive source layout or build
2294 system (for example, a package that builds the same source
2295 multiple times to generate different binary packages).
2301 <chapt id="controlfields">
2302 <heading>Control files and their fields</heading>
2305 The package management system manipulates data represented in
2306 a common format, known as <em>control data</em>, stored in
2307 <em>control files</em>.
2308 Control files are used for source packages, binary packages and
2309 the <file>.changes</file> files which control the installation
2310 of uploaded files<footnote>
2311 <prgn>dpkg</prgn>'s internal databases are in a similar
2316 <sect id="controlsyntax">
2317 <heading>Syntax of control files</heading>
2320 A control file consists of one or more paragraphs of
2322 The paragraphs are also sometimes referred to as stanzas.
2324 The paragraphs are separated by blank lines. Some control
2325 files allow only one paragraph; others allow several, in
2326 which case each paragraph usually refers to a different
2327 package. (For example, in source packages, the first
2328 paragraph refers to the source package, and later paragraphs
2329 refer to binary packages generated from the source.)
2333 Each paragraph consists of a series of data fields; each
2334 field consists of the field name, followed by a colon and
2335 then the data/value associated with that field. It ends at
2336 the end of the (logical) line. Horizontal whitespace
2337 (spaces and tabs) may occur immediately before or after the
2338 value and is ignored there; it is conventional to put a
2339 single space after the colon. For example, a field might
2341 <example compact="compact">
2344 the field name is <tt>Package</tt> and the field value
2349 Many fields' values may span several lines; in this case
2350 each continuation line must start with a space or a tab.
2351 Any trailing spaces or tabs at the end of individual
2352 lines of a field value are ignored.
2356 In fields where it is specified that lines may not wrap,
2357 only a single line of data is allowed and whitespace is not
2358 significant in a field body. Whitespace must not appear
2359 inside names (of packages, architectures, files or anything
2360 else) or version numbers, or between the characters of
2361 multi-character version relationships.
2365 Field names are not case-sensitive, but it is usual to
2366 capitalize the field names using mixed case as shown below.
2370 Blank lines, or lines consisting only of spaces and tabs,
2371 are not allowed within field values or between fields - that
2372 would mean a new paragraph.
2376 All control files must be encoded in UTF-8.
2380 <sect id="sourcecontrolfiles">
2381 <heading>Source package control files -- <file>debian/control</file></heading>
2384 The <file>debian/control</file> file contains the most vital
2385 (and version-independent) information about the source package
2386 and about the binary packages it creates.
2390 The first paragraph of the control file contains information about
2391 the source package in general. The subsequent sets each describe a
2392 binary package that the source tree builds.
2396 The fields in the general paragraph (the first one, for the source
2399 <list compact="compact">
2400 <item><qref id="f-Source"><tt>Source</tt></qref> (mandatory)</item>
2401 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
2402 <item><qref id="f-Uploaders"><tt>Uploaders</tt></qref></item>
2403 <item><qref id="f-Section"><tt>Section</tt></qref> (recommended)</item>
2404 <item><qref id="f-Priority"><tt>Priority</tt></qref> (recommended)</item>
2405 <item><qref id="sourcebinarydeps"><tt>Build-Depends</tt> et al</qref></item>
2406 <item><qref id="f-Standards-Version"><tt>Standards-Version</tt></qref> (recommended)</item>
2407 <item><qref id="f-Homepage"><tt>Homepage</tt></qref></item>
2412 The fields in the binary package paragraphs are:
2414 <list compact="compact">
2415 <item><qref id="f-Package"><tt>Package</tt></qref> (mandatory)</item>
2416 <item><qref id="f-Architecture"><tt>Architecture</tt></qref> (mandatory)</item>
2417 <item><qref id="f-Section"><tt>Section</tt></qref> (recommended)</item>
2418 <item><qref id="f-Priority"><tt>Priority</tt></qref> (recommended)</item>
2419 <item><qref id="f-Essential"><tt>Essential</tt></qref></item>
2420 <item><qref id="binarydeps"><tt>Depends</tt> et al</qref></item>
2421 <item><qref id="f-Description"><tt>Description</tt></qref> (mandatory)</item>
2422 <item><qref id="f-Homepage"><tt>Homepage</tt></qref></item>
2427 The syntax and semantics of the fields are described below.
2433 These fields are used by <prgn>dpkg-gencontrol</prgn> to
2434 generate control files for binary packages (see below), by
2435 <prgn>dpkg-genchanges</prgn> to generate the
2436 <tt>.changes</tt> file to accompany the upload, and by
2437 <prgn>dpkg-source</prgn> when it creates the
2438 <file>.dsc</file> source control file as part of a source
2439 archive. Many fields are permitted to span multiple lines in
2440 <file>debian/control</file> but not in any other control
2441 file. These tools are responsible for removing the line
2442 breaks from such fields when using fields from
2443 <file>debian/control</file> to generate other control files.
2447 The fields here may contain variable references - their
2448 values will be substituted by <prgn>dpkg-gencontrol</prgn>,
2449 <prgn>dpkg-genchanges</prgn> or <prgn>dpkg-source</prgn>
2450 when they generate output control files.
2451 See <ref id="substvars"> for details.
2455 In addition to the control file syntax described <qref
2456 id="controlsyntax">above</qref>, this file may also contain
2457 comment lines starting with <tt>#</tt> without any preceding
2458 whitespace. All such lines are ignored, even in the middle of
2459 continuation lines for a multiline field, and do not end a
2465 <sect id="binarycontrolfiles">
2466 <heading>Binary package control files -- <file>DEBIAN/control</file></heading>
2469 The <file>DEBIAN/control</file> file contains the most vital
2470 (and version-dependent) information about a binary package.
2474 The fields in this file are:
2476 <list compact="compact">
2477 <item><qref id="f-Package"><tt>Package</tt></qref> (mandatory)</item>
2478 <item><qref id="f-Source"><tt>Source</tt></qref></item>
2479 <item><qref id="f-Version"><tt>Version</tt></qref> (mandatory)</item>
2480 <item><qref id="f-Section"><tt>Section</tt></qref> (recommended)</item>
2481 <item><qref id="f-Priority"><tt>Priority</tt></qref> (recommended)</item>
2482 <item><qref id="f-Architecture"><tt>Architecture</tt></qref> (mandatory)</item>
2483 <item><qref id="f-Essential"><tt>Essential</tt></qref></item>
2484 <item><qref id="binarydeps"><tt>Depends</tt> et al</qref></item>
2485 <item><qref id="f-Installed-Size"><tt>Installed-Size</tt></qref></item>
2486 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
2487 <item><qref id="f-Description"><tt>Description</tt></qref> (mandatory)</item>
2488 <item><qref id="f-Homepage"><tt>Homepage</tt></qref></item>
2493 <sect id="debiansourcecontrolfiles">
2494 <heading>Debian source control files -- <tt>.dsc</tt></heading>
2497 This file contains a series of fields, identified and
2498 separated just like the fields in the control file of
2499 a binary package. The fields are listed below; their
2500 syntax is described above, in <ref id="pkg-controlfields">.
2502 <list compact="compact">
2503 <item><qref id="f-Format"><tt>Format</tt></qref> (mandatory)</item>
2504 <item><qref id="f-Source"><tt>Source</tt></qref> (mandatory)</item>
2505 <item><qref id="f-Version"><tt>Version</tt></qref> (mandatory)</item>
2506 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
2507 <item><qref id="f-Uploaders"><tt>Uploaders</tt></qref></item>
2508 <item><qref id="f-Binary"><tt>Binary</tt></qref></item>
2509 <item><qref id="f-Architecture"><tt>Architecture</tt></qref></item>
2510 <item><qref id="sourcebinarydeps"><tt>Build-Depends</tt> et al</qref></item>
2511 <item><qref id="f-Standards-Version"><tt>Standards-Version</tt></qref> (recommended)</item>
2512 <item><qref id="f-Files"><tt>Files</tt></qref> (mandatory)</item>
2513 <item><qref id="f-Homepage"><tt>Homepage</tt></qref></item>
2518 The source package control file is generated by
2519 <prgn>dpkg-source</prgn> when it builds the source
2520 archive, from other files in the source package,
2521 described above. When unpacking, it is checked against
2522 the files and directories in the other parts of the
2528 <sect id="debianchangesfiles">
2529 <heading>Debian changes files -- <file>.changes</file></heading>
2532 The .changes files are used by the Debian archive maintenance
2533 software to process updates to packages. They contain one
2534 paragraph which contains information from the
2535 <tt>debian/control</tt> file and other data about the
2536 source package gathered via <tt>debian/changelog</tt>
2537 and <tt>debian/rules</tt>.
2541 The fields in this file are:
2543 <list compact="compact">
2544 <item><qref id="f-Format"><tt>Format</tt></qref> (mandatory)</item>
2545 <item><qref id="f-Date"><tt>Date</tt></qref> (mandatory)</item>
2546 <item><qref id="f-Source"><tt>Source</tt></qref> (mandatory)</item>
2547 <item><qref id="f-Binary"><tt>Binary</tt></qref> (mandatory)</item>
2548 <item><qref id="f-Architecture"><tt>Architecture</tt></qref> (mandatory)</item>
2549 <item><qref id="f-Version"><tt>Version</tt></qref> (mandatory)</item>
2550 <item><qref id="f-Distribution"><tt>Distribution</tt></qref> (mandatory)</item>
2551 <item><qref id="f-Urgency"><tt>Urgency</tt></qref> (recommended)</item>
2552 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
2553 <item><qref id="f-Changed-By"><tt>Changed-By</tt></qref></item>
2554 <item><qref id="f-Description"><tt>Description</tt></qref> (mandatory)</item>
2555 <item><qref id="f-Closes"><tt>Closes</tt></qref></item>
2556 <item><qref id="f-Changes"><tt>Changes</tt></qref> (mandatory)</item>
2557 <item><qref id="f-Files"><tt>Files</tt></qref> (mandatory)</item>
2562 <sect id="controlfieldslist">
2563 <heading>List of fields</heading>
2565 <sect1 id="f-Source">
2566 <heading><tt>Source</tt></heading>
2569 This field identifies the source package name.
2573 In <file>debian/control</file> or a <file>.dsc</file> file,
2574 this field must contain only the name of the source package.
2578 In a binary package control file or a <file>.changes</file>
2579 file, the source package name may be followed by a version
2580 number in parentheses<footnote>
2581 It is customary to leave a space after the package name
2582 if a version number is specified.
2584 This version number may be omitted (and is, by
2585 <prgn>dpkg-gencontrol</prgn>) if it has the same value as
2586 the <tt>Version</tt> field of the binary package in
2587 question. The field itself may be omitted from a binary
2588 package control file when the source package has the same
2589 name and version as the binary package.
2593 Package names must consist only of lower case letters
2594 (<tt>a-z</tt>), digits (<tt>0-9</tt>), plus (<tt>+</tt>)
2595 and minus (<tt>-</tt>) signs, and periods (<tt>.</tt>).
2596 They must be at least two characters long and must start
2597 with an alphanumeric character.
2601 <sect1 id="f-Maintainer">
2602 <heading><tt>Maintainer</tt></heading>
2605 The package maintainer's name and email address. The name
2606 should come first, then the email address inside angle
2607 brackets <tt><></tt> (in RFC822 format).
2611 If the maintainer's name contains a full stop then the
2612 whole field will not work directly as an email address due
2613 to a misfeature in the syntax specified in RFC822; a
2614 program using this field as an address must check for this
2615 and correct the problem if necessary (for example by
2616 putting the name in round brackets and moving it to the
2617 end, and bringing the email address forward).
2621 <sect1 id="f-Uploaders">
2622 <heading><tt>Uploaders</tt></heading>
2625 List of the names and email addresses of co-maintainers of
2626 the package, if any. If the package has other maintainers
2627 beside the one named in the
2628 <qref id="f-Maintainer">Maintainer field</qref>, their
2629 names and email addresses should be listed here. The
2630 format is the same as that of the Maintainer tag, and
2631 multiple entries should be comma separated. Currently,
2632 this field is restricted to a single line of data. This
2633 is an optional field.
2636 Any parser that interprets the Uploaders field in
2637 <file>debian/control</file> must permit it to span multiple
2638 lines. Line breaks in an Uploaders field that spans multiple
2639 lines are not significant and the semantics of the field are
2640 the same as if the line breaks had not been present.
2644 <sect1 id="f-Changed-By">
2645 <heading><tt>Changed-By</tt></heading>
2648 The name and email address of the person who changed the
2649 said package. Usually the name of the maintainer.
2650 All the rules for the Maintainer field apply here, too.
2654 <sect1 id="f-Section">
2655 <heading><tt>Section</tt></heading>
2658 This field specifies an application area into which the package
2659 has been classified. See <ref id="subsections">.
2663 When it appears in the <file>debian/control</file> file,
2664 it gives the value for the subfield of the same name in
2665 the <tt>Files</tt> field of the <file>.changes</file> file.
2666 It also gives the default for the same field in the binary
2671 <sect1 id="f-Priority">
2672 <heading><tt>Priority</tt></heading>
2675 This field represents how important that it is that the user
2676 have the package installed. See <ref id="priorities">.
2680 When it appears in the <file>debian/control</file> file,
2681 it gives the value for the subfield of the same name in
2682 the <tt>Files</tt> field of the <file>.changes</file> file.
2683 It also gives the default for the same field in the binary
2688 <sect1 id="f-Package">
2689 <heading><tt>Package</tt></heading>
2692 The name of the binary package.
2696 Package names must consist only of lower case letters
2697 (<tt>a-z</tt>), digits (<tt>0-9</tt>), plus (<tt>+</tt>)
2698 and minus (<tt>-</tt>) signs, and periods (<tt>.</tt>).
2699 They must be at least two characters long and must start
2700 with an alphanumeric character.
2704 <sect1 id="f-Architecture">
2705 <heading><tt>Architecture</tt></heading>
2708 Depending on context and the control file used, the
2709 <tt>Architecture</tt> field can include the following sets of
2712 <item>A unique single word identifying a Debian machine
2713 architecture, see <ref id="arch-spec">.
2714 <item><tt>all</tt>, which indicates an
2715 architecture-independent package.
2716 <item><tt>any</tt>, which indicates a package available
2717 for building on any architecture.
2718 <item><tt>source</tt>, which indicates a source package.
2723 In the main <file>debian/control</file> file in the source
2724 package, or in the source package control file
2725 <file>.dsc</file>, one may specify a list of architectures
2726 separated by spaces, or the special values <tt>any</tt> or
2731 Specifying <tt>any</tt> indicates that the source package
2732 isn't dependent on any particular architecture and should
2733 compile fine on any one. The produced binary package(s)
2734 will be specific to whatever the current build architecture
2736 This is the most often used setting, and is recommended
2737 for new packages that aren't <tt>Architecture: all</tt>.
2742 Specifying a list of architectures indicates that the source
2743 will build an architecture-dependent package, and will only
2744 work correctly on the listed architectures.<footnote>
2745 This is a setting used for a minority of cases where the
2746 program is not portable. Generally, it should not be used
2752 In a <file>.changes</file> file, the <tt>Architecture</tt>
2753 field lists the architecture(s) of the package(s)
2754 currently being uploaded. This will be a list; if the
2755 source for the package is also being uploaded, the special
2756 entry <tt>source</tt> is also present.
2760 See <ref id="debianrules"> for information how to get the
2761 architecture for the build process.
2765 <sect1 id="f-Essential">
2766 <heading><tt>Essential</tt></heading>
2769 This is a boolean field which may occur only in the
2770 control file of a binary package or in a per-package fields
2771 paragraph of a main source control data file.
2775 If set to <tt>yes</tt> then the package management system
2776 will refuse to remove the package (upgrading and replacing
2777 it is still possible). The other possible value is <tt>no</tt>,
2778 which is the same as not having the field at all.
2783 <heading>Package interrelationship fields:
2784 <tt>Depends</tt>, <tt>Pre-Depends</tt>,
2785 <tt>Recommends</tt>, <tt>Suggests</tt>,
2786 <tt>Breaks</tt>, <tt>Conflicts</tt>,
2787 <tt>Provides</tt>, <tt>Replaces</tt>, <tt>Enhances</tt>
2791 These fields describe the package's relationships with
2792 other packages. Their syntax and semantics are described
2793 in <ref id="relationships">.</p>
2796 <sect1 id="f-Standards-Version">
2797 <heading><tt>Standards-Version</tt></heading>
2800 The most recent version of the standards (the policy
2801 manual and associated texts) with which the package
2806 The version number has four components: major and minor
2807 version number and major and minor patch level. When the
2808 standards change in a way that requires every package to
2809 change the major number will be changed. Significant
2810 changes that will require work in many packages will be
2811 signaled by a change to the minor number. The major patch
2812 level will be changed for any change to the meaning of the
2813 standards, however small; the minor patch level will be
2814 changed when only cosmetic, typographical or other edits
2815 are made which neither change the meaning of the document
2816 nor affect the contents of packages.
2820 Thus only the first three components of the policy version
2821 are significant in the <em>Standards-Version</em> control
2822 field, and so either these three components or the all
2823 four components may be specified.<footnote>
2824 In the past, people specified the full version number
2825 in the Standards-Version field, for example "2.3.0.0".
2826 Since minor patch-level changes don't introduce new
2827 policy, it was thought it would be better to relax
2828 policy and only require the first 3 components to be
2829 specified, in this example "2.3.0". All four
2830 components may still be used if someone wishes to do so.
2836 <sect1 id="f-Version">
2837 <heading><tt>Version</tt></heading>
2840 The version number of a package. The format is:
2841 [<var>epoch</var><tt>:</tt>]<var>upstream_version</var>[<tt>-</tt><var>debian_revision</var>]
2845 The three components here are:
2847 <tag><var>epoch</var></tag>
2850 This is a single (generally small) unsigned integer. It
2851 may be omitted, in which case zero is assumed. If it is
2852 omitted then the <var>upstream_version</var> may not
2857 It is provided to allow mistakes in the version numbers
2858 of older versions of a package, and also a package's
2859 previous version numbering schemes, to be left behind.
2863 <tag><var>upstream_version</var></tag>
2866 This is the main part of the version number. It is
2867 usually the version number of the original ("upstream")
2868 package from which the <file>.deb</file> file has been made,
2869 if this is applicable. Usually this will be in the same
2870 format as that specified by the upstream author(s);
2871 however, it may need to be reformatted to fit into the
2872 package management system's format and comparison
2877 The comparison behavior of the package management system
2878 with respect to the <var>upstream_version</var> is
2879 described below. The <var>upstream_version</var>
2880 portion of the version number is mandatory.
2884 The <var>upstream_version</var> may contain only
2885 alphanumerics<footnote>
2886 Alphanumerics are <tt>A-Za-z0-9</tt> only.
2888 and the characters <tt>.</tt> <tt>+</tt> <tt>-</tt>
2889 <tt>:</tt> <tt>~</tt> (full stop, plus, hyphen, colon,
2890 tilde) and should start with a digit. If there is no
2891 <var>debian_revision</var> then hyphens are not allowed;
2892 if there is no <var>epoch</var> then colons are not
2897 <tag><var>debian_revision</var></tag>
2900 This part of the version number specifies the version of
2901 the Debian package based on the upstream version. It
2902 may contain only alphanumerics and the characters
2903 <tt>+</tt> <tt>.</tt> <tt>~</tt> (plus, full stop,
2904 tilde) and is compared in the same way as the
2905 <var>upstream_version</var> is.
2909 It is optional; if it isn't present then the
2910 <var>upstream_version</var> may not contain a hyphen.
2911 This format represents the case where a piece of
2912 software was written specifically to be turned into a
2913 Debian package, and so there is only one "debianisation"
2914 of it and therefore no revision indication is required.
2918 It is conventional to restart the
2919 <var>debian_revision</var> at <tt>1</tt> each time the
2920 <var>upstream_version</var> is increased.
2924 The package management system will break the version
2925 number apart at the last hyphen in the string (if there
2926 is one) to determine the <var>upstream_version</var> and
2927 <var>debian_revision</var>. The absence of a
2928 <var>debian_revision</var> is equivalent to a
2929 <var>debian_revision</var> of <tt>0</tt>.
2936 When comparing two version numbers, first the <var>epoch</var>
2937 of each are compared, then the <var>upstream_version</var> if
2938 <var>epoch</var> is equal, and then <var>debian_revision</var>
2939 if <var>upstream_version</var> is also equal.
2940 <var>epoch</var> is compared numerically. The
2941 <var>upstream_version</var> and <var>debian_revision</var>
2942 parts are compared by the package management system using the
2943 following algorithm:
2947 The strings are compared from left to right.
2951 First the initial part of each string consisting entirely of
2952 non-digit characters is determined. These two parts (one of
2953 which may be empty) are compared lexically. If a difference
2954 is found it is returned. The lexical comparison is a
2955 comparison of ASCII values modified so that all the letters
2956 sort earlier than all the non-letters and so that a tilde
2957 sorts before anything, even the end of a part. For example,
2958 the following parts are in sorted order from earliest to
2959 latest: <tt>~~</tt>, <tt>~~a</tt>, <tt>~</tt>, the empty part,
2960 <tt>a</tt>.<footnote>
2961 One common use of <tt>~</tt> is for upstream pre-releases.
2962 For example, <tt>1.0~beta1~svn1245</tt> sorts earlier than
2963 <tt>1.0~beta1</tt>, which sorts earlier than <tt>1.0</tt>.
2968 Then the initial part of the remainder of each string which
2969 consists entirely of digit characters is determined. The
2970 numerical values of these two parts are compared, and any
2971 difference found is returned as the result of the comparison.
2972 For these purposes an empty string (which can only occur at
2973 the end of one or both version strings being compared) counts
2978 These two steps (comparing and removing initial non-digit
2979 strings and initial digit strings) are repeated until a
2980 difference is found or both strings are exhausted.
2984 Note that the purpose of epochs is to allow us to leave behind
2985 mistakes in version numbering, and to cope with situations
2986 where the version numbering scheme changes. It is
2987 <em>not</em> intended to cope with version numbers containing
2988 strings of letters which the package management system cannot
2989 interpret (such as <tt>ALPHA</tt> or <tt>pre-</tt>), or with
2990 silly orderings (the author of this manual has heard of a
2991 package whose versions went <tt>1.1</tt>, <tt>1.2</tt>,
2992 <tt>1.3</tt>, <tt>1</tt>, <tt>2.1</tt>, <tt>2.2</tt>,
2993 <tt>2</tt> and so forth).
2997 <sect1 id="f-Description">
2998 <heading><tt>Description</tt></heading>
3001 In a source or binary control file, the <tt>Description</tt>
3002 field contains a description of the binary package, consisting
3003 of two parts, the synopsis or the short description, and the
3004 long description. The field's format is as follows:
3009 Description: <single line synopsis>
3010 <extended description over several lines>
3015 The lines in the extended description can have these formats:
3021 Those starting with a single space are part of a paragraph.
3022 Successive lines of this form will be word-wrapped when
3023 displayed. The leading space will usually be stripped off.
3027 Those starting with two or more spaces. These will be
3028 displayed verbatim. If the display cannot be panned
3029 horizontally, the displaying program will line wrap them "hard"
3030 (i.e., without taking account of word breaks). If it can they
3031 will be allowed to trail off to the right. None, one or two
3032 initial spaces may be deleted, but the number of spaces
3033 deleted from each line will be the same (so that you can have
3034 indenting work correctly, for example).
3038 Those containing a single space followed by a single full stop
3039 character. These are rendered as blank lines. This is the
3040 <em>only</em> way to get a blank line<footnote>
3041 Completely empty lines will not be rendered as blank lines.
3042 Instead, they will cause the parser to think you're starting
3043 a whole new record in the control file, and will therefore
3044 likely abort with an error.
3049 Those containing a space, a full stop and some more characters.
3050 These are for future expansion. Do not use them.
3056 Do not use tab characters. Their effect is not predictable.
3060 See <ref id="descriptions"> for further information on this.
3064 In a <file>.changes</file> file, the <tt>Description</tt> field
3065 contains a summary of the descriptions for the packages being
3070 The part of the field before the first newline is empty;
3071 thereafter each line has the name of a binary package and
3072 the summary description line from that binary package.
3073 Each line is indented by one space.
3078 <sect1 id="f-Distribution">
3079 <heading><tt>Distribution</tt></heading>
3082 In a <file>.changes</file> file or parsed changelog output
3083 this contains the (space-separated) name(s) of the
3084 distribution(s) where this version of the package should
3085 be installed. Valid distributions are determined by the
3086 archive maintainers.<footnote>
3087 Current distribution names are:
3088 <taglist compact="compact">
3089 <tag><em>stable</em></tag>
3091 This is the current "released" version of Debian
3092 GNU/Linux. Once the distribution is
3093 <em>stable</em> only security fixes and other
3094 major bug fixes are allowed. When changes are
3095 made to this distribution, the release number is
3096 increased (for example: 2.2r1 becomes 2.2r2 then
3100 <tag><em>unstable</em></tag>
3102 This distribution value refers to the
3103 <em>developmental</em> part of the Debian
3104 distribution tree. New packages, new upstream
3105 versions of packages and bug fixes go into the
3106 <em>unstable</em> directory tree. Download from
3107 this distribution at your own risk.
3110 <tag><em>testing</em></tag>
3112 This distribution value refers to the
3113 <em>testing</em> part of the Debian distribution
3114 tree. It receives its packages from the
3115 unstable distribution after a short time lag to
3116 ensure that there are no major issues with the
3117 unstable packages. It is less prone to breakage
3118 than unstable, but still risky. It is not
3119 possible to upload packages directly to
3123 <tag><em>frozen</em></tag>
3125 From time to time, the <em>testing</em>
3126 distribution enters a state of "code-freeze" in
3127 anticipation of release as a <em>stable</em>
3128 version. During this period of testing only
3129 fixes for existing or newly-discovered bugs will
3130 be allowed. The exact details of this stage are
3131 determined by the Release Manager.
3134 <tag><em>experimental</em></tag>
3136 The packages with this distribution value are
3137 deemed by their maintainers to be high
3138 risk. Oftentimes they represent early beta or
3139 developmental packages from various sources that
3140 the maintainers want people to try, but are not
3141 ready to be a part of the other parts of the
3142 Debian distribution tree. Download at your own
3148 You should list <em>all</em> distributions that the
3149 package should be installed into.
3153 More information is available in the Debian Developer's
3154 Reference, section "The Debian archive".
3161 <heading><tt>Date</tt></heading>
3164 This field includes the date the package was built or last edited.
3168 The value of this field is usually extracted from the
3169 <file>debian/changelog</file> file - see
3170 <ref id="dpkgchangelog">).
3174 <sect1 id="f-Format">
3175 <heading><tt>Format</tt></heading>
3178 This field specifies a format revision for the file.
3179 The most current format described in the Policy Manual
3180 is version <strong>1.5</strong>. The syntax of the
3181 format value is the same as that of a package version
3182 number except that no epoch or Debian revision is allowed
3183 - see <ref id="f-Version">.
3187 <sect1 id="f-Urgency">
3188 <heading><tt>Urgency</tt></heading>
3191 This is a description of how important it is to upgrade to
3192 this version from previous ones. It consists of a single
3193 keyword taking one of the values <tt>low</tt>,
3194 <tt>medium</tt>, <tt>high</tt>, <tt>emergency</tt>, or
3195 <tt>critical</tt><footnote>
3196 Other urgency values are supported with configuration
3197 changes in the archive software but are not used in Debian.
3198 The urgency affects how quickly a package will be considered
3199 for inclusion into the <tt>testing</tt> distribution and
3200 gives an indication of the importance of any fixes included
3201 in the upload. <tt>Emergency</tt> and <tt>critical</tt> are
3202 treated as synonymous.
3203 </footnote> (not case-sensitive) followed by an optional
3204 commentary (separated by a space) which is usually in
3205 parentheses. For example:
3208 Urgency: low (HIGH for users of diversions)
3214 The value of this field is usually extracted from the
3215 <file>debian/changelog</file> file - see
3216 <ref id="dpkgchangelog">.
3220 <sect1 id="f-Changes">
3221 <heading><tt>Changes</tt></heading>
3224 This field contains the human-readable changes data, describing
3225 the differences between the last version and the current one.
3229 There should be nothing in this field before the first
3230 newline; all the subsequent lines must be indented by at
3231 least one space; blank lines must be represented by a line
3232 consisting only of a space and a full stop.
3236 The value of this field is usually extracted from the
3237 <file>debian/changelog</file> file - see
3238 <ref id="dpkgchangelog">).
3242 Each version's change information should be preceded by a
3243 "title" line giving at least the version, distribution(s)
3244 and urgency, in a human-readable way.
3248 If data from several versions is being returned the entry
3249 for the most recent version should be returned first, and
3250 entries should be separated by the representation of a
3251 blank line (the "title" line may also be followed by the
3252 representation of blank line).
3256 <sect1 id="f-Binary">
3257 <heading><tt>Binary</tt></heading>
3260 This field is a list of binary packages.
3264 When it appears in the <file>.dsc</file> file it is the list
3265 of binary packages which a source package can produce. It
3266 does not necessarily produce all of these binary packages
3267 for every architecture. The source control file doesn't
3268 contain details of which architectures are appropriate for
3269 which of the binary packages.
3273 When it appears in a <file>.changes</file> file it lists the
3274 names of the binary packages actually being uploaded.
3278 The syntax is a list of binary packages separated by
3280 A space after each comma is conventional.
3281 </footnote>. Currently the packages must be separated using
3282 only spaces in the <file>.changes</file> file.
3286 <sect1 id="f-Installed-Size">
3287 <heading><tt>Installed-Size</tt></heading>
3290 This field appears in the control files of binary
3291 packages, and in the <file>Packages</file> files. It gives
3292 the total amount of disk space required to install the
3297 The disk space is represented in kilobytes as a simple
3302 <sect1 id="f-Files">
3303 <heading><tt>Files</tt></heading>
3306 This field contains a list of files with information about
3307 each one. The exact information and syntax varies with
3308 the context. In all cases the part of the field
3309 contents on the same line as the field name is empty. The
3310 remainder of the field is one line per file, each line
3311 being indented by one space and containing a number of
3312 sub-fields separated by spaces.
3316 In the <file>.dsc</file> file, each line contains the MD5
3317 checksum, size and filename of the tar file and (if applicable)
3318 diff file which make up the remainder of the source
3320 That is, the parts which are not the <tt>.dsc</tt>.
3322 The exact forms of the filenames are described
3323 in <ref id="pkg-sourcearchives">.
3327 In the <file>.changes</file> file this contains one line per
3328 file being uploaded. Each line contains the MD5 checksum,
3329 size, section and priority and the filename.
3330 The <qref id="f-Section">section</qref>
3331 and <qref id="f-Priority">priority</qref>
3332 are the values of the corresponding fields in
3333 the main source control file. If no section or priority is
3334 specified then <tt>-</tt> should be used, though section
3335 and priority values must be specified for new packages to
3336 be installed properly.
3340 The special value <tt>byhand</tt> for the section in a
3341 <tt>.changes</tt> file indicates that the file in question
3342 is not an ordinary package file and must by installed by
3343 hand by the distribution maintainers. If the section is
3344 <tt>byhand</tt> the priority should be <tt>-</tt>.
3348 If a new Debian revision of a package is being shipped and
3349 no new original source archive is being distributed the
3350 <tt>.dsc</tt> must still contain the <tt>Files</tt> field
3351 entry for the original source archive
3352 <file><var>package</var>-<var>upstream-version</var>.orig.tar.gz</file>,
3353 but the <file>.changes</file> file should leave it out. In
3354 this case the original source archive on the distribution
3355 site must match exactly, byte-for-byte, the original
3356 source archive which was used to generate the
3357 <file>.dsc</file> file and diff which are being uploaded.</p>
3360 <sect1 id="f-Closes">
3361 <heading><tt>Closes</tt></heading>
3364 A space-separated list of bug report numbers that the upload
3365 governed by the .changes file closes.
3369 <sect1 id="f-Homepage">
3370 <heading><tt>Homepage</tt></heading>
3373 The URL of the web site for this package, preferably (when
3374 applicable) the site from which the original source can be
3375 obtained and any additional upstream documentation or
3376 information may be found. The content of this field is a
3377 simple URL without any surrounding characters such as
3385 <heading>User-defined fields</heading>
3388 Additional user-defined fields may be added to the
3389 source package control file. Such fields will be
3390 ignored, and not copied to (for example) binary or
3391 source package control files or upload control files.
3395 If you wish to add additional unsupported fields to
3396 these output files you should use the mechanism
3401 Fields in the main source control information file with
3402 names starting <tt>X</tt>, followed by one or more of
3403 the letters <tt>BCS</tt> and a hyphen <tt>-</tt>, will
3404 be copied to the output files. Only the part of the
3405 field name after the hyphen will be used in the output
3406 file. Where the letter <tt>B</tt> is used the field
3407 will appear in binary package control files, where the
3408 letter <tt>S</tt> is used in source package control
3409 files and where <tt>C</tt> is used in upload control
3410 (<tt>.changes</tt>) files.
3414 For example, if the main source information control file
3417 XBS-Comment: I stand between the candle and the star.
3419 then the binary and source package control files will contain the
3422 Comment: I stand between the candle and the star.
3431 <chapt id="maintainerscripts">
3432 <heading>Package maintainer scripts and installation procedure</heading>
3435 <heading>Introduction to package maintainer scripts</heading>
3438 It is possible to supply scripts as part of a package which
3439 the package management system will run for you when your
3440 package is installed, upgraded or removed.
3444 These scripts are the files <prgn>preinst</prgn>,
3445 <prgn>postinst</prgn>, <prgn>prerm</prgn> and
3446 <prgn>postrm</prgn> in the control area of the package.
3447 They must be proper executable files; if they are scripts
3448 (which is recommended), they must start with the usual
3449 <tt>#!</tt> convention. They should be readable and
3450 executable by anyone, and must not be world-writable.
3454 The package management system looks at the exit status from
3455 these scripts. It is important that they exit with a
3456 non-zero status if there is an error, so that the package
3457 management system can stop its processing. For shell
3458 scripts this means that you <em>almost always</em> need to
3459 use <tt>set -e</tt> (this is usually true when writing shell
3460 scripts, in fact). It is also important, of course, that
3461 they exit with a zero status if everything went well.
3465 Additionally, packages interacting with users using
3466 <tt>debconf</tt> in the <prgn>postinst</prgn> script should
3467 install a <prgn>config</prgn> script in the control area,
3468 see <ref id="maintscriptprompt"> for details.
3472 When a package is upgraded a combination of the scripts from
3473 the old and new packages is called during the upgrade
3474 procedure. If your scripts are going to be at all
3475 complicated you need to be aware of this, and may need to
3476 check the arguments to your scripts.
3480 Broadly speaking the <prgn>preinst</prgn> is called before
3481 (a particular version of) a package is installed, and the
3482 <prgn>postinst</prgn> afterwards; the <prgn>prerm</prgn>
3483 before (a version of) a package is removed and the
3484 <prgn>postrm</prgn> afterwards.
3488 Programs called from maintainer scripts should not normally
3489 have a path prepended to them. Before installation is
3490 started, the package management system checks to see if the
3491 programs <prgn>ldconfig</prgn>,
3492 <prgn>start-stop-daemon</prgn>, <prgn>install-info</prgn>,
3493 and <prgn>update-rc.d</prgn> can be found via the
3494 <tt>PATH</tt> environment variable. Those programs, and any
3495 other program that one would expect to be in the
3496 <tt>PATH</tt>, should thus be invoked without an absolute
3497 pathname. Maintainer scripts should also not reset the
3498 <tt>PATH</tt>, though they might choose to modify it by
3499 prepending or appending package-specific directories. These
3500 considerations really apply to all shell scripts.</p>
3503 <sect id="idempotency">
3504 <heading>Maintainer scripts idempotency</heading>
3507 It is necessary for the error recovery procedures that the
3508 scripts be idempotent. This means that if it is run
3509 successfully, and then it is called again, it doesn't bomb
3510 out or cause any harm, but just ensures that everything is
3511 the way it ought to be. If the first call failed, or
3512 aborted half way through for some reason, the second call
3513 should merely do the things that were left undone the first
3514 time, if any, and exit with a success status if everything
3516 This is so that if an error occurs, the user interrupts
3517 <prgn>dpkg</prgn> or some other unforeseen circumstance
3518 happens you don't leave the user with a badly-broken
3519 package when <prgn>dpkg</prgn> attempts to repeat the
3525 <sect id="controllingterminal">
3526 <heading>Controlling terminal for maintainer scripts</heading>
3529 The maintainer scripts are guaranteed to run with a
3530 controlling terminal and can interact with the user.
3531 Because these scripts may be executed with standard output
3532 redirected into a pipe for logging purposes, Perl scripts
3533 should set unbuffered output by setting <tt>$|=1</tt> so
3534 that the output is printed immediately rather than being
3538 <sect id="exitstatus">
3539 <heading>Exit status</heading>
3542 Each script must return a zero exit status for
3543 success, or a nonzero one for failure, since the package
3544 management system looks for the exit status of these scripts
3545 and determines what action to take next based on that datum.
3549 <sect id="mscriptsinstact"><heading>Summary of ways maintainer
3554 <list compact="compact">
3556 <var>new-preinst</var> <tt>install</tt>
3559 <var>new-preinst</var> <tt>install</tt> <var>old-version</var>
3562 <var>new-preinst</var> <tt>upgrade</tt> <var>old-version</var>
3565 <var>old-preinst</var> <tt>abort-upgrade</tt>
3566 <var>new-version</var>
3571 <list compact="compact">
3573 <var>postinst</var> <tt>configure</tt>
3574 <var>most-recently-configured-version</var>
3577 <var>old-postinst</var> <tt>abort-upgrade</tt>
3578 <var>new-version</var>
3581 <var>conflictor's-postinst</var> <tt>abort-remove</tt>
3582 <tt>in-favour</tt> <var>package</var>
3583 <var>new-version</var>
3586 <var>postinst</var> <tt>abort-remove</tt>
3589 <var>deconfigured's-postinst</var>
3590 <tt>abort-deconfigure</tt> <tt>in-favour</tt>
3591 <var>failed-install-package</var> <var>version</var>
3592 [<tt>removing</tt> <var>conflicting-package</var>
3598 <list compact="compact">
3600 <var>prerm</var> <tt>remove</tt>
3603 <var>old-prerm</var> <tt>upgrade</tt>
3604 <var>new-version</var>
3607 <var>new-prerm</var> <tt>failed-upgrade</tt>
3608 <var>old-version</var>
3611 <var>conflictor's-prerm</var> <tt>remove</tt>
3612 <tt>in-favour</tt> <var>package</var>
3613 <var>new-version</var>
3616 <var>deconfigured's-prerm</var> <tt>deconfigure</tt>
3617 <tt>in-favour</tt> <var>package-being-installed</var>
3618 <var>version</var> [<tt>removing</tt>
3619 <var>conflicting-package</var>
3625 <list compact="compact">
3627 <var>postrm</var> <tt>remove</tt>
3630 <var>postrm</var> <tt>purge</tt>
3633 <var>old-postrm</var> <tt>upgrade</tt>
3634 <var>new-version</var>
3637 <var>new-postrm</var> <tt>failed-upgrade</tt>
3638 <var>old-version</var>
3641 <var>new-postrm</var> <tt>abort-install</tt>
3644 <var>new-postrm</var> <tt>abort-install</tt>
3645 <var>old-version</var>
3648 <var>new-postrm</var> <tt>abort-upgrade</tt>
3649 <var>old-version</var>
3652 <var>disappearer's-postrm</var> <tt>disappear</tt>
3653 <var>overwriter</var>
3654 <var>overwriter-version</var>
3660 <sect id="unpackphase">
3661 <heading>Details of unpack phase of installation or upgrade</heading>
3664 The procedure on installation/upgrade/overwrite/disappear
3665 (i.e., when running <tt>dpkg --unpack</tt>, or the unpack
3666 stage of <tt>dpkg --install</tt>) is as follows. In each
3667 case, if a major error occurs (unless listed below) the
3668 actions are, in general, run backwards - this means that the
3669 maintainer scripts are run with different arguments in
3670 reverse order. These are the "error unwind" calls listed
3677 If a version of the package is already installed, call
3678 <example compact="compact">
3679 <var>old-prerm</var> upgrade <var>new-version</var>
3683 If the script runs but exits with a non-zero
3684 exit status, <prgn>dpkg</prgn> will attempt:
3685 <example compact="compact">
3686 <var>new-prerm</var> failed-upgrade <var>old-version</var>
3688 If this works, the upgrade continues. If this
3689 does not work, the error unwind:
3690 <example compact="compact">
3691 <var>old-postinst</var> abort-upgrade <var>new-version</var>
3693 If this works, then the old-version is
3694 "Installed", if not, the old version is in a
3695 "Failed-Config" state.
3701 If a "conflicting" package is being removed at the same time,
3702 or if any package will be broken (due to <tt>Breaks</tt>):
3705 If <tt>--auto-deconfigure</tt> is
3706 specified, call, for each package to be deconfigured
3707 due to <tt>Breaks</tt>:
3708 <example compact="compact">
3709 <var>deconfigured's-prerm</var> deconfigure \
3710 in-favour <var>package-being-installed</var> <var>version</var>
3713 <example compact="compact">
3714 <var>deconfigured's-postinst</var> abort-deconfigure \
3715 in-favour <var>package-being-installed-but-failed</var> <var>version</var>
3717 The deconfigured packages are marked as
3718 requiring configuration, so that if
3719 <tt>--install</tt> is used they will be
3720 configured again if possible.
3723 If any packages depended on a conflicting
3724 package being removed and <tt>--auto-deconfigure</tt> is
3725 specified, call, for each such package:
3726 <example compact="compact">
3727 <var>deconfigured's-prerm</var> deconfigure \
3728 in-favour <var>package-being-installed</var> <var>version</var> \
3729 removing <var>conflicting-package</var> <var>version</var>
3732 <example compact="compact">
3733 <var>deconfigured's-postinst</var> abort-deconfigure \
3734 in-favour <var>package-being-installed-but-failed</var> <var>version</var> \
3735 removing <var>conflicting-package</var> <var>version</var>
3737 The deconfigured packages are marked as
3738 requiring configuration, so that if
3739 <tt>--install</tt> is used they will be
3740 configured again if possible.
3743 To prepare for removal of each conflicting package, call:
3744 <example compact="compact">
3745 <var>conflictor's-prerm</var> remove \
3746 in-favour <var>package</var> <var>new-version</var>
3749 <example compact="compact">
3750 <var>conflictor's-postinst</var> abort-remove \
3751 in-favour <var>package</var> <var>new-version</var>
3760 If the package is being upgraded, call:
3761 <example compact="compact">
3762 <var>new-preinst</var> upgrade <var>old-version</var>
3764 If this fails, we call:
3766 <var>new-postrm</var> abort-upgrade <var>old-version</var>
3773 <var>old-postinst</var> abort-upgrade <var>new-version</var>
3775 is called. If this works, then the old version
3776 is in an "Installed" state, or else it is left
3777 in an "Unpacked" state.
3782 If it fails, then the old version is left
3783 in an "Half-Installed" state.
3790 Otherwise, if the package had some configuration
3791 files from a previous version installed (i.e., it
3792 is in the "configuration files only" state):
3793 <example compact="compact">
3794 <var>new-preinst</var> install <var>old-version</var>
3798 <var>new-postrm</var> abort-install <var>old-version</var>
3800 If this fails, the package is left in a
3801 "Half-Installed" state, which requires a
3802 reinstall. If it works, the packages is left in
3803 a "Config Files" state.
3806 Otherwise (i.e., the package was completely purged):
3807 <example compact="compact">
3808 <var>new-preinst</var> install
3811 <example compact="compact">
3812 <var>new-postrm</var> abort-install
3814 If the error-unwind fails, the package is in a
3815 "Half Installed" phase, and requires a
3816 reinstall. If the error unwind works, the
3817 package is in a not installed state.
3824 The new package's files are unpacked, overwriting any
3825 that may be on the system already, for example any
3826 from the old version of the same package or from
3827 another package. Backups of the old files are kept
3828 temporarily, and if anything goes wrong the package
3829 management system will attempt to put them back as
3830 part of the error unwind.
3834 It is an error for a package to contain files which
3835 are on the system in another package, unless
3836 <tt>Replaces</tt> is used (see <ref id="replaces">).
3838 The following paragraph is not currently the case:
3839 Currently the <tt>- - force-overwrite</tt> flag is
3840 enabled, downgrading it to a warning, but this may not
3846 It is a more serious error for a package to contain a
3847 plain file or other kind of non-directory where another
3848 package has a directory (again, unless
3849 <tt>Replaces</tt> is used). This error can be
3850 overridden if desired using
3851 <tt>--force-overwrite-dir</tt>, but this is not
3856 Packages which overwrite each other's files produce
3857 behavior which, though deterministic, is hard for the
3858 system administrator to understand. It can easily
3859 lead to "missing" programs if, for example, a package
3860 is installed which overwrites a file from another
3861 package, and is then removed again.<footnote>
3862 Part of the problem is due to what is arguably a
3863 bug in <prgn>dpkg</prgn>.
3868 A directory will never be replaced by a symbolic link
3869 to a directory or vice versa; instead, the existing
3870 state (symlink or not) will be left alone and
3871 <prgn>dpkg</prgn> will follow the symlink if there is
3880 If the package is being upgraded, call
3881 <example compact="compact">
3882 <var>old-postrm</var> upgrade <var>new-version</var>
3886 If this fails, <prgn>dpkg</prgn> will attempt:
3887 <example compact="compact">
3888 <var>new-postrm</var> failed-upgrade <var>old-version</var>
3890 If this works, installation continues. If not,
3892 <example compact="compact">
3893 <var>old-preinst</var> abort-upgrade <var>new-version</var>
3895 If this fails, the old version is left in an
3896 "Half Installed" state. If it works, dpkg now
3898 <example compact="compact">
3899 <var>new-postrm</var> abort-upgrade <var>old-version</var>
3901 If this fails, the old version is left in an
3902 "Half Installed" state. If it works, dpkg now
3904 <example compact="compact">
3905 <var>old-postinst</var> abort-upgrade <var>new-version</var>
3907 If this fails, the old version is in an
3914 This is the point of no return - if
3915 <prgn>dpkg</prgn> gets this far, it won't back off
3916 past this point if an error occurs. This will
3917 leave the package in a fairly bad state, which
3918 will require a successful re-installation to clear
3919 up, but it's when <prgn>dpkg</prgn> starts doing
3920 things that are irreversible.
3925 Any files which were in the old version of the package
3926 but not in the new are removed.
3930 The new file list replaces the old.
3934 The new maintainer scripts replace the old.
3938 Any packages all of whose files have been overwritten
3939 during the installation, and which aren't required for
3940 dependencies, are considered to have been removed.
3941 For each such package
3944 <prgn>dpkg</prgn> calls:
3945 <example compact="compact">
3946 <var>disappearer's-postrm</var> disappear \
3947 <var>overwriter</var> <var>overwriter-version</var>
3951 The package's maintainer scripts are removed.
3954 It is noted in the status database as being in a
3955 sane state, namely not installed (any conffiles
3956 it may have are ignored, rather than being
3957 removed by <prgn>dpkg</prgn>). Note that
3958 disappearing packages do not have their prerm
3959 called, because <prgn>dpkg</prgn> doesn't know
3960 in advance that the package is going to
3967 Any files in the package we're unpacking that are also
3968 listed in the file lists of other packages are removed
3969 from those lists. (This will lobotomize the file list
3970 of the "conflicting" package if there is one.)
3974 The backup files made during installation, above, are
3980 The new package's status is now sane, and recorded as
3985 Here is another point of no return - if the
3986 conflicting package's removal fails we do not unwind
3987 the rest of the installation; the conflicting package
3988 is left in a half-removed limbo.
3993 If there was a conflicting package we go and do the
3994 removal actions (described below), starting with the
3995 removal of the conflicting package's files (any that
3996 are also in the package being installed have already
3997 been removed from the conflicting package's file list,
3998 and so do not get removed now).
4004 <sect id="configdetails"><heading>Details of configuration</heading>
4007 When we configure a package (this happens with <tt>dpkg
4008 --install</tt> and <tt>dpkg --configure</tt>), we first
4009 update any <tt>conffile</tt>s and then call:
4010 <example compact="compact">
4011 <var>postinst</var> configure <var>most-recently-configured-version</var>
4016 No attempt is made to unwind after errors during
4017 configuration. If the configuration fails, the package is in
4018 a "Failed Config" state, and an error message is generated.
4022 If there is no most recently configured version
4023 <prgn>dpkg</prgn> will pass a null argument.
4026 Historical note: Truly ancient (pre-1997) versions of
4027 <prgn>dpkg</prgn> passed <tt><unknown></tt>
4028 (including the angle brackets) in this case. Even older
4029 ones did not pass a second argument at all, under any
4030 circumstance. Note that upgrades using such an old dpkg
4031 version are unlikely to work for other reasons, even if
4032 this old argument behavior is handled by your postinst script.
4038 <sect id="removedetails"><heading>Details of removal and/or
4039 configuration purging</heading>
4045 <example compact="compact">
4046 <var>prerm</var> remove
4050 If prerm fails during replacement due to conflict
4052 <var>conflictor's-postinst</var> abort-remove \
4053 in-favour <var>package</var> <var>new-version</var>
4057 <var>postinst</var> abort-remove
4061 If this fails, the package is in a "Failed-Config"
4062 state, or else it remains "Installed".
4066 The package's files are removed (except <tt>conffile</tt>s).
4069 <example compact="compact">
4070 <var>postrm</var> remove
4074 If it fails, there's no error unwind, and the package is in
4075 an "Half-Installed" state.
4080 All the maintainer scripts except the <prgn>postrm</prgn>
4085 If we aren't purging the package we stop here. Note
4086 that packages which have no <prgn>postrm</prgn> and no
4087 <tt>conffile</tt>s are automatically purged when
4088 removed, as there is no difference except for the
4089 <prgn>dpkg</prgn> status.
4093 The <tt>conffile</tt>s and any backup files
4094 (<tt>~</tt>-files, <tt>#*#</tt> files,
4095 <tt>%</tt>-files, <tt>.dpkg-{old,new,tmp}</tt>, etc.)
4100 <example compact="compact">
4101 <var>postrm</var> purge
4105 If this fails, the package remains in a "Config-Files"
4110 The package's file list is removed.
4119 <chapt id="relationships">
4120 <heading>Declaring relationships between packages</heading>
4122 <sect id="depsyntax">
4123 <heading>Syntax of relationship fields</heading>
4126 These fields all have a uniform syntax. They are a list of
4127 package names separated by commas.
4131 In the <tt>Depends</tt>, <tt>Recommends</tt>,
4132 <tt>Suggests</tt>, <tt>Pre-Depends</tt>,
4133 <tt>Build-Depends</tt> and <tt>Build-Depends-Indep</tt>
4134 control file fields of the package, which declare
4135 dependencies on other packages, the package names listed may
4136 also include lists of alternative package names, separated
4137 by vertical bar (pipe) symbols <tt>|</tt>. In such a case,
4138 if any one of the alternative packages is installed, that
4139 part of the dependency is considered to be satisfied.
4143 All of the fields except for <tt>Provides</tt> may restrict
4144 their applicability to particular versions of each named
4145 package. This is done in parentheses after each individual
4146 package name; the parentheses should contain a relation from
4147 the list below followed by a version number, in the format
4148 described in <ref id="f-Version">.
4152 The relations allowed are <tt><<</tt>, <tt><=</tt>,
4153 <tt>=</tt>, <tt>>=</tt> and <tt>>></tt> for
4154 strictly earlier, earlier or equal, exactly equal, later or
4155 equal and strictly later, respectively. The deprecated
4156 forms <tt><</tt> and <tt>></tt> were used to mean
4157 earlier/later or equal, rather than strictly earlier/later,
4158 so they should not appear in new packages (though
4159 <prgn>dpkg</prgn> still supports them).
4163 Whitespace may appear at any point in the version
4164 specification subject to the rules in <ref
4165 id="controlsyntax">, and must appear where it's necessary to
4166 disambiguate; it is not otherwise significant. All of the
4167 relationship fields may span multiple lines. For
4168 consistency and in case of future changes to
4169 <prgn>dpkg</prgn> it is recommended that a single space be
4170 used after a version relationship and before a version
4171 number; it is also conventional to put a single space after
4172 each comma, on either side of each vertical bar, and before
4173 each open parenthesis. When wrapping a relationship field, it
4174 is conventional to do so after a comma and before the space
4175 following that comma.
4179 For example, a list of dependencies might appear as:
4180 <example compact="compact">
4183 Depends: libc6 (>= 2.2.1), exim | mail-transport-agent
4188 All fields that specify build-time relationships
4189 (<tt>Build-Depends</tt>, <tt>Build-Depends-Indep</tt>,
4190 <tt>Build-Conflicts</tt> and <tt>Build-Conflicts-Indep</tt>)
4191 may be restricted to a certain set of architectures. This
4192 is indicated in brackets after each individual package name and
4193 the optional version specification. The brackets enclose a
4194 list of Debian architecture names separated by whitespace.
4195 Exclamation marks may be prepended to each of the names.
4196 (It is not permitted for some names to be prepended with
4197 exclamation marks while others aren't.) If the current Debian
4198 host architecture is not in this list and there are no
4199 exclamation marks in the list, or it is in the list with a
4200 prepended exclamation mark, the package name and the
4201 associated version specification are ignored completely for
4202 the purposes of defining the relationships.
4207 <example compact="compact">
4209 Build-Depends-Indep: texinfo
4210 Build-Depends: kernel-headers-2.2.10 [!hurd-i386],
4211 hurd-dev [hurd-i386], gnumach-dev [hurd-i386]
4213 requires <tt>kernel-headers-2.2.10</tt> on all architectures
4214 other than hurd-i386 and requires <tt>hurd-dev</tt> and
4215 <tt>gnumach-dev</tt> only on hurd-i386.
4219 If the architecture-restricted dependency is part of a set of
4220 alternatives using <tt>|</tt>, that alternative is ignored
4221 completely on architectures that do not match the restriction.
4223 <example compact="compact">
4224 Build-Depends: foo [!i386] | bar [!amd64]
4226 is equivalent to <tt>bar</tt> on the i386 architecture, to
4227 <tt>foo</tt> on the amd64 architecture, and to <tt>foo |
4228 bar</tt> on all other architectures.
4232 Note that the binary package relationship fields such as
4233 <tt>Depends</tt> appear in one of the binary package
4234 sections of the control file, whereas the build-time
4235 relationships such as <tt>Build-Depends</tt> appear in the
4236 source package section of the control file (which is the
4241 <sect id="binarydeps">
4242 <heading>Binary Dependencies - <tt>Depends</tt>,
4243 <tt>Recommends</tt>, <tt>Suggests</tt>, <tt>Enhances</tt>,
4244 <tt>Pre-Depends</tt>
4248 Packages can declare in their control file that they have
4249 certain relationships to other packages - for example, that
4250 they may not be installed at the same time as certain other
4251 packages, and/or that they depend on the presence of others.
4255 This is done using the <tt>Depends</tt>, <tt>Pre-Depends</tt>,
4256 <tt>Recommends</tt>, <tt>Suggests</tt>, <tt>Enhances</tt>,
4257 <tt>Breaks</tt> and <tt>Conflicts</tt> control file fields.
4261 These seven fields are used to declare a dependency
4262 relationship by one package on another. Except for
4263 <tt>Enhances</tt> and <tt>Breaks</tt>, they appear in the
4264 depending (binary) package's control file.
4265 (<tt>Enhances</tt> appears in the recommending package's
4266 control file, and <tt>Breaks</tt> appears in the version of
4267 depended-on package which causes the named package to
4272 A <tt>Depends</tt> field takes effect <em>only</em> when a
4273 package is to be configured. It does not prevent a package
4274 being on the system in an unconfigured state while its
4275 dependencies are unsatisfied, and it is possible to replace
4276 a package whose dependencies are satisfied and which is
4277 properly installed with a different version whose
4278 dependencies are not and cannot be satisfied; when this is
4279 done the depending package will be left unconfigured (since
4280 attempts to configure it will give errors) and will not
4281 function properly. If it is necessary, a
4282 <tt>Pre-Depends</tt> field can be used, which has a partial
4283 effect even when a package is being unpacked, as explained
4284 in detail below. (The other three dependency fields,
4285 <tt>Recommends</tt>, <tt>Suggests</tt> and
4286 <tt>Enhances</tt>, are only used by the various front-ends
4287 to <prgn>dpkg</prgn> such as <prgn>apt-get</prgn>,
4288 <prgn>aptitude</prgn>, and <prgn>dselect</prgn>.)
4292 For this reason packages in an installation run are usually
4293 all unpacked first and all configured later; this gives
4294 later versions of packages with dependencies on later
4295 versions of other packages the opportunity to have their
4296 dependencies satisfied.
4300 In case of circular dependencies, since installation or
4301 removal order honoring the dependency order can't be
4302 established, dependency loops are broken at some point
4303 (based on rules below), and some packages may not be able to
4304 rely on their dependencies being present when being
4305 installed or removed, depending on which side of the break
4306 of the circular dependency loop they happen to be on. If one
4307 of the packages in the loop has no postinst script, then the
4308 cycle will be broken at that package, so as to ensure that
4309 all postinst scripts run with the dependencies properly
4310 configured if this is possible. Otherwise the breaking point
4315 The <tt>Depends</tt> field thus allows package maintainers
4316 to impose an order in which packages should be configured.
4320 The meaning of the five dependency fields is as follows:
4322 <tag><tt>Depends</tt></tag>
4325 This declares an absolute dependency. A package will
4326 not be configured unless all of the packages listed in
4327 its <tt>Depends</tt> field have been correctly
4332 The <tt>Depends</tt> field should be used if the
4333 depended-on package is required for the depending
4334 package to provide a significant amount of
4339 The <tt>Depends</tt> field should also be used if the
4340 <prgn>postinst</prgn>, <prgn>prerm</prgn> or
4341 <prgn>postrm</prgn> scripts require the package to be
4342 present in order to run. Note, however, that the
4343 <prgn>postrm</prgn> cannot rely on any non-essential
4344 packages to be present during the <tt>purge</tt>
4348 <tag><tt>Recommends</tt></tag>
4351 This declares a strong, but not absolute, dependency.
4355 The <tt>Recommends</tt> field should list packages
4356 that would be found together with this one in all but
4357 unusual installations.
4361 <tag><tt>Suggests</tt></tag>
4363 This is used to declare that one package may be more
4364 useful with one or more others. Using this field
4365 tells the packaging system and the user that the
4366 listed packages are related to this one and can
4367 perhaps enhance its usefulness, but that installing
4368 this one without them is perfectly reasonable.
4371 <tag><tt>Enhances</tt></tag>
4373 This field is similar to Suggests but works in the
4374 opposite direction. It is used to declare that a
4375 package can enhance the functionality of another
4379 <tag><tt>Pre-Depends</tt></tag>
4382 This field is like <tt>Depends</tt>, except that it
4383 also forces <prgn>dpkg</prgn> to complete installation
4384 of the packages named before even starting the
4385 installation of the package which declares the
4386 pre-dependency, as follows:
4390 When a package declaring a pre-dependency is about to
4391 be <em>unpacked</em> the pre-dependency can be
4392 satisfied if the depended-on package is either fully
4393 configured, <em>or even if</em> the depended-on
4394 package(s) are only unpacked or half-configured,
4395 provided that they have been configured correctly at
4396 some point in the past (and not removed or partially
4397 removed since). In this case, both the
4398 previously-configured and currently unpacked or
4399 half-configured versions must satisfy any version
4400 clause in the <tt>Pre-Depends</tt> field.
4404 When the package declaring a pre-dependency is about
4405 to be <em>configured</em>, the pre-dependency will be
4406 treated as a normal <tt>Depends</tt>, that is, it will
4407 be considered satisfied only if the depended-on
4408 package has been correctly configured.
4412 <tt>Pre-Depends</tt> should be used sparingly,
4413 preferably only by packages whose premature upgrade or
4414 installation would hamper the ability of the system to
4415 continue with any upgrade that might be in progress.
4419 <tt>Pre-Depends</tt> are also required if the
4420 <prgn>preinst</prgn> script depends on the named
4421 package. It is best to avoid this situation if
4429 When selecting which level of dependency to use you should
4430 consider how important the depended-on package is to the
4431 functionality of the one declaring the dependency. Some
4432 packages are composed of components of varying degrees of
4433 importance. Such a package should list using
4434 <tt>Depends</tt> the package(s) which are required by the
4435 more important components. The other components'
4436 requirements may be mentioned as Suggestions or
4437 Recommendations, as appropriate to the components' relative
4443 <heading>Packages which break other packages - <tt>Breaks</tt></heading>
4446 Using <tt>Breaks</tt> may cause problems for upgrades from older
4447 versions of Debian and should not be used until the stable
4448 release of Debian supports <tt>Breaks</tt>.
4452 When one binary package declares that it breaks another,
4453 <prgn>dpkg</prgn> will refuse to allow the package which
4454 declares <tt>Breaks</tt> be installed unless the broken
4455 package is deconfigured first, and it will refuse to
4456 allow the broken package to be reconfigured.
4460 A package will not be regarded as causing breakage merely
4461 because its configuration files are still installed; it must
4462 be at least half-installed.
4466 A special exception is made for packages which declare that
4467 they break their own package name or a virtual package which
4468 they provide (see below): this does not count as a real
4473 Normally a <tt>Breaks</tt> entry will have an "earlier than"
4474 version clause; such a <tt>Breaks</tt> is introduced in the
4475 version of an (implicit or explicit) dependency which
4476 violates an assumption or reveals a bug in earlier versions
4477 of the broken package. This use of <tt>Breaks</tt> will
4478 inform higher-level package management tools that broken
4479 package must be upgraded before the new one.
4483 If the breaking package also overwrites some files from the
4484 older package, it should use <tt>Replaces</tt> (not
4485 <tt>Conflicts</tt>) to ensure this goes smoothly.
4489 <sect id="conflicts">
4490 <heading>Conflicting binary packages - <tt>Conflicts</tt></heading>
4493 When one binary package declares a conflict with another
4494 using a <tt>Conflicts</tt> field, <prgn>dpkg</prgn> will
4495 refuse to allow them to be installed on the system at the
4500 If one package is to be installed, the other must be removed
4501 first - if the package being installed is marked as
4502 replacing (see <ref id="replaces">) the one on the system,
4503 or the one on the system is marked as deselected, or both
4504 packages are marked <tt>Essential</tt>, then
4505 <prgn>dpkg</prgn> will automatically remove the package
4506 which is causing the conflict, otherwise it will halt the
4507 installation of the new package with an error. This
4508 mechanism is specifically designed to produce an error when
4509 the installed package is <tt>Essential</tt>, but the new
4514 A package will not cause a conflict merely because its
4515 configuration files are still installed; it must be at least
4520 A special exception is made for packages which declare a
4521 conflict with their own package name, or with a virtual
4522 package which they provide (see below): this does not
4523 prevent their installation, and allows a package to conflict
4524 with others providing a replacement for it. You use this
4525 feature when you want the package in question to be the only
4526 package providing some feature.
4530 A <tt>Conflicts</tt> entry should almost never have an
4531 "earlier than" version clause. This would prevent
4532 <prgn>dpkg</prgn> from upgrading or installing the package
4533 which declared such a conflict until the upgrade or removal
4534 of the conflicted-with package had been completed. Instead,
4535 <tt>Breaks</tt> may be used.
4539 <sect id="virtual"><heading>Virtual packages - <tt>Provides</tt>
4543 As well as the names of actual ("concrete") packages, the
4544 package relationship fields <tt>Depends</tt>,
4545 <tt>Recommends</tt>, <tt>Suggests</tt>, <tt>Enhances</tt>,
4546 <tt>Pre-Depends</tt>, <tt>Breaks</tt>, <tt>Conflicts</tt>,
4547 <tt>Build-Depends</tt>, <tt>Build-Depends-Indep</tt>,
4548 <tt>Build-Conflicts</tt> and <tt>Build-Conflicts-Indep</tt>
4549 may mention "virtual packages".
4553 A <em>virtual package</em> is one which appears in the
4554 <tt>Provides</tt> control file field of another package.
4555 The effect is as if the package(s) which provide a
4556 particular virtual package name had been listed by name
4557 everywhere the virtual package name appears. (See also <ref
4562 If there are both concrete and virtual packages of the same
4563 name, then the dependency may be satisfied (or the conflict
4564 caused) by either the concrete package with the name in
4565 question or any other concrete package which provides the
4566 virtual package with the name in question. This is so that,
4567 for example, supposing we have
4568 <example compact="compact">
4571 </example> and someone else releases an enhanced version of
4572 the <tt>bar</tt> package they can say:
4573 <example compact="compact">
4577 and the <tt>bar-plus</tt> package will now also satisfy the
4578 dependency for the <tt>foo</tt> package.
4582 If a relationship field has a version number attached
4583 then only real packages will be considered to see whether
4584 the relationship is satisfied (or the prohibition violated,
4585 for a conflict or breakage) - it is assumed that a real
4586 package which provides the virtual package is not of the
4587 "right" version. So, a <tt>Provides</tt> field may not
4588 contain version numbers, and the version number of the
4589 concrete package which provides a particular virtual package
4590 will not be looked at when considering a dependency on or
4591 conflict with the virtual package name.
4595 It is likely that the ability will be added in a future
4596 release of <prgn>dpkg</prgn> to specify a version number for
4597 each virtual package it provides. This feature is not yet
4598 present, however, and is expected to be used only
4603 If you want to specify which of a set of real packages
4604 should be the default to satisfy a particular dependency on
4605 a virtual package, you should list the real package as an
4606 alternative before the virtual one.
4611 <sect id="replaces"><heading>Overwriting files and replacing
4612 packages - <tt>Replaces</tt></heading>
4615 Packages can declare in their control file that they should
4616 overwrite files in certain other packages, or completely
4617 replace other packages. The <tt>Replaces</tt> control file
4618 field has these two distinct purposes.
4621 <sect1><heading>Overwriting files in other packages</heading>
4624 Firstly, as mentioned before, it is usually an error for a
4625 package to contain files which are on the system in
4630 However, if the overwriting package declares that it
4631 <tt>Replaces</tt> the one containing the file being
4632 overwritten, then <prgn>dpkg</prgn> will replace the file
4633 from the old package with that from the new. The file
4634 will no longer be listed as "owned" by the old package.
4638 If a package is completely replaced in this way, so that
4639 <prgn>dpkg</prgn> does not know of any files it still
4640 contains, it is considered to have "disappeared". It will
4641 be marked as not wanted on the system (selected for
4642 removal) and not installed. Any <tt>conffile</tt>s
4643 details noted for the package will be ignored, as they
4644 will have been taken over by the overwriting package. The
4645 package's <prgn>postrm</prgn> script will be run with a
4646 special argument to allow the package to do any final
4647 cleanup required. See <ref id="mscriptsinstact">.
4650 Replaces is a one way relationship -- you have to
4651 install the replacing package after the replaced
4658 For this usage of <tt>Replaces</tt>, virtual packages (see
4659 <ref id="virtual">) are not considered when looking at a
4660 <tt>Replaces</tt> field - the packages declared as being
4661 replaced must be mentioned by their real names.
4665 Furthermore, this usage of <tt>Replaces</tt> only takes
4666 effect when both packages are at least partially on the
4667 system at once, so that it can only happen if they do not
4668 conflict or if the conflict has been overridden.
4673 <sect1><heading>Replacing whole packages, forcing their
4677 Secondly, <tt>Replaces</tt> allows the packaging system to
4678 resolve which package should be removed when there is a
4679 conflict - see <ref id="conflicts">. This usage only
4680 takes effect when the two packages <em>do</em> conflict,
4681 so that the two usages of this field do not interfere with
4686 In this situation, the package declared as being replaced
4687 can be a virtual package, so for example, all mail
4688 transport agents (MTAs) would have the following fields in
4689 their control files:
4690 <example compact="compact">
4691 Provides: mail-transport-agent
4692 Conflicts: mail-transport-agent
4693 Replaces: mail-transport-agent
4695 ensuring that only one MTA can be installed at any one
4700 <sect id="sourcebinarydeps">
4701 <heading>Relationships between source and binary packages -
4702 <tt>Build-Depends</tt>, <tt>Build-Depends-Indep</tt>,
4703 <tt>Build-Conflicts</tt>, <tt>Build-Conflicts-Indep</tt>
4707 Source packages that require certain binary packages to be
4708 installed or absent at the time of building the package
4709 can declare relationships to those binary packages.
4713 This is done using the <tt>Build-Depends</tt>,
4714 <tt>Build-Depends-Indep</tt>, <tt>Build-Conflicts</tt> and
4715 <tt>Build-Conflicts-Indep</tt> control file fields.
4719 Build-dependencies on "build-essential" binary packages can be
4720 omitted. Please see <ref id="pkg-relations"> for more information.
4724 The dependencies and conflicts they define must be satisfied
4725 (as defined earlier for binary packages) in order to invoke
4726 the targets in <tt>debian/rules</tt>, as follows:<footnote>
4728 If you make "build-arch" or "binary-arch", you need
4729 Build-Depends. If you make "build-indep" or
4730 "binary-indep", you need Build-Depends and
4731 Build-Depends-Indep. If you make "build" or "binary",
4735 There is no Build-Depends-Arch; this role is essentially
4736 met with Build-Depends. Anyone building the
4737 <tt>build-indep</tt> and binary-indep<tt></tt> targets
4738 is basically assumed to be building the whole package
4739 anyway and so installs all build dependencies. The
4740 autobuilders use <tt>dpkg-buildpackage -B</tt>, which
4741 calls <tt>build</tt> (not <tt>build-arch</tt>, since it
4742 does not yet know how to check for its existence) and
4743 <tt>binary-arch</tt>.
4746 The purpose of the original split, I recall, was so that
4747 the autobuilders wouldn't need to install extra packages
4748 needed only for the binary-indep targets. But without a
4749 build-arch/build-indep split, this didn't work, since
4750 most of the work is done in the build target, not in the
4756 <tag><tt>Build-Depends</tt>, <tt>Build-Conflicts</tt></tag>
4758 The <tt>Build-Depends</tt> and
4759 <tt>Build-Conflicts</tt> fields must be satisfied when
4760 any of the following targets is invoked:
4761 <tt>build</tt>, <tt>clean</tt>, <tt>binary</tt>,
4762 <tt>binary-arch</tt>, <tt>build-arch</tt>,
4763 <tt>build-indep</tt> and <tt>binary-indep</tt>.
4765 <tag><tt>Build-Depends-Indep</tt>,
4766 <tt>Build-Conflicts-Indep</tt></tag>
4768 The <tt>Build-Depends-Indep</tt> and
4769 <tt>Build-Conflicts-Indep</tt> fields must be
4770 satisfied when any of the following targets is
4771 invoked: <tt>build</tt>, <tt>build-indep</tt>,
4772 <tt>binary</tt> and <tt>binary-indep</tt>.
4782 <chapt id="sharedlibs"><heading>Shared libraries</heading>
4785 Packages containing shared libraries must be constructed with
4786 a little care to make sure that the shared library is always
4787 available. This is especially important for packages whose
4788 shared libraries are vitally important, such as the C library
4789 (currently <tt>libc6</tt>).
4793 Packages involving shared libraries should be split up into
4794 several binary packages. This section mostly deals with how
4795 this separation is to be accomplished; rules for files within
4796 the shared library packages are in <ref id="libraries"> instead.
4799 <sect id="sharedlibs-runtime">
4800 <heading>Run-time shared libraries</heading>
4803 The run-time shared library needs to be placed in a package
4804 whose name changes whenever the shared object version
4807 Since it is common place to install several versions of a
4808 package that just provides shared libraries, it is a
4809 good idea that the library package should not
4810 contain any extraneous non-versioned files, unless they
4811 happen to be in versioned directories.</p>
4813 The most common mechanism is to place it in a package
4815 <package><var>libraryname</var><var>soversion</var></package>,
4816 where <file><var>soversion</var></file> is the version number
4817 in the soname of the shared library<footnote>
4818 The soname is the shared object name: it's the thing
4819 that has to match exactly between building an executable
4820 and running it for the dynamic linker to be able run the
4821 program. For example, if the soname of the library is
4822 <file>libfoo.so.6</file>, the library package would be
4823 called <file>libfoo6</file>.
4825 Alternatively, if it would be confusing to directly append
4826 <var>soversion</var> to <var>libraryname</var> (e.g. because
4827 <var>libraryname</var> itself ends in a number), you may use
4828 <package><var>libraryname</var>-<var>soversion</var></package> and
4829 <package><var>libraryname</var>-<var>soversion</var>-dev</package>
4834 If you have several shared libraries built from the same
4835 source tree you may lump them all together into a single
4836 shared library package, provided that you change all of
4837 their sonames at once (so that you don't get filename
4838 clashes if you try to install different versions of the
4839 combined shared libraries package).
4843 The package should install the shared libraries under
4844 their normal names. For example, the <package>libgdbm3</package>
4845 package should install <file>libgdbm.so.3.0.0</file> as
4846 <file>/usr/lib/libgdbm.so.3.0.0</file>. The files should not be
4847 renamed or re-linked by any <prgn>prerm</prgn> or
4848 <prgn>postrm</prgn> scripts; <prgn>dpkg</prgn> will take care
4849 of renaming things safely without affecting running programs,
4850 and attempts to interfere with this are likely to lead to
4855 Shared libraries should not be installed executable, since
4856 the dynamic linker does not require this and trying to
4857 execute a shared library usually results in a core dump.
4861 The run-time library package should include the symbolic link that
4862 <prgn>ldconfig</prgn> would create for the shared libraries.
4863 For example, the <package>libgdbm3</package> package should include
4864 a symbolic link from <file>/usr/lib/libgdbm.so.3</file> to
4865 <file>libgdbm.so.3.0.0</file>. This is needed so that the dynamic
4866 linker (for example <prgn>ld.so</prgn> or
4867 <prgn>ld-linux.so.*</prgn>) can find the library between the
4868 time that <prgn>dpkg</prgn> installs it and the time that
4869 <prgn>ldconfig</prgn> is run in the <prgn>postinst</prgn>
4871 The package management system requires the library to be
4872 placed before the symbolic link pointing to it in the
4873 <file>.deb</file> file. This is so that when
4874 <prgn>dpkg</prgn> comes to install the symlink
4875 (overwriting the previous symlink pointing at an older
4876 version of the library), the new shared library is already
4877 in place. In the past, this was achieved by creating the
4878 library in the temporary packaging directory before
4879 creating the symlink. Unfortunately, this was not always
4880 effective, since the building of the tar file in the
4881 <file>.deb</file> depended on the behavior of the underlying
4882 file system. Some file systems (such as reiserfs) reorder
4883 the files so that the order of creation is forgotten.
4884 Since version 1.7.0, <prgn>dpkg</prgn>
4885 reorders the files itself as necessary when building a
4886 package. Thus it is no longer important to concern
4887 oneself with the order of file creation.
4891 <sect1 id="ldconfig">
4892 <heading><tt>ldconfig</tt></heading>
4895 Any package installing shared libraries in one of the default
4896 library directories of the dynamic linker (which are currently
4897 <file>/usr/lib</file> and <file>/lib</file>) or a directory that is
4898 listed in <file>/etc/ld.so.conf</file><footnote>
4900 <list compact="compact">
4901 <item>/usr/local/lib</item>
4902 <item>/usr/lib/libc5-compat</item>
4903 <item>/lib/libc5-compat</item>
4906 must use <prgn>ldconfig</prgn> to update the shared library
4911 The package maintainer scripts must only call
4912 <prgn>ldconfig</prgn> under these circumstances:
4913 <list compact="compact">
4914 <item>When the <prgn>postinst</prgn> script is run with a
4915 first argument of <tt>configure</tt>, the script must call
4916 <prgn>ldconfig</prgn>, and may optionally invoke
4917 <prgn>ldconfig</prgn> at other times.
4919 <item>When the <prgn>postrm</prgn> script is run with a
4920 first argument of <tt>remove</tt>, the script should call
4921 <prgn>ldconfig</prgn>.
4926 During install or upgrade, the preinst is called before
4927 the new files are installed, so calling "ldconfig" is
4928 pointless. The preinst of an existing package can also be
4929 called if an upgrade fails. However, this happens during
4930 the critical time when a shared libs may exist on-disk
4931 under a temporary name. Thus, it is dangerous and
4932 forbidden by current policy to call "ldconfig" at this
4937 When a package is installed or upgraded, "postinst
4938 configure" runs after the new files are safely on-disk.
4939 Since it is perfectly safe to invoke ldconfig
4940 unconditionally in a postinst, it is OK for a package to
4941 simply put ldconfig in its postinst without checking the
4942 argument. The postinst can also be called to recover from
4943 a failed upgrade. This happens before any new files are
4944 unpacked, so there is no reason to call "ldconfig" at this
4949 For a package that is being removed, prerm is
4950 called with all the files intact, so calling ldconfig is
4951 useless. The other calls to "prerm" happen in the case of
4952 upgrade at a time when all the files of the old package
4953 are on-disk, so again calling "ldconfig" is pointless.
4957 postrm, on the other hand, is called with the "remove"
4958 argument just after the files are removed, so this is
4959 the proper time to call "ldconfig" to notify the system
4960 of the fact that the shared libraries from the package
4961 are removed. The postrm can be called at several other
4962 times. At the time of "postrm purge", "postrm
4963 abort-install", or "postrm abort-upgrade", calling
4964 "ldconfig" is useless because the shared lib files are
4965 not on-disk. However, when "postrm" is invoked with
4966 arguments "upgrade", "failed-upgrade", or "disappear", a
4967 shared lib may exist on-disk under a temporary filename.
4975 <sect id="sharedlibs-support-files">
4976 <heading>Shared library support files</heading>
4979 If your package contains files whose names do not change with
4980 each change in the library shared object version, you must not
4981 put them in the shared library package. Otherwise, several
4982 versions of the shared library cannot be installed at the same
4983 time without filename clashes, making upgrades and transitions
4984 unnecessarily difficult.
4988 It is recommended that supporting files and run-time support
4989 programs that do not need to be invoked manually by users, but
4990 are nevertheless required for the package to function, be placed
4991 (if they are binary) in a subdirectory of <file>/usr/lib</file>,
4992 preferably under <file>/usr/lib/</file><var>package-name</var>.
4993 If the program or file is architecture independent, the
4994 recommendation is for it to be placed in a subdirectory of
4995 <file>/usr/share</file> instead, preferably under
4996 <file>/usr/share/</file><var>package-name</var>. Following the
4997 <var>package-name</var> naming convention ensures that the file
4998 names change when the shared object version changes.
5002 Run-time support programs that use the shared library but are
5003 not required for the library to function or files used by the
5004 shared library that can be used by any version of the shared
5005 library package should instead be put in a separate package.
5006 This package might typically be named
5007 <package><var>libraryname</var>-tools</package>; note the
5008 absence of the <var>soversion</var> in the package name.
5012 Files and support programs only useful when compiling software
5013 against the library should be included in the development
5014 package for the library.<footnote>
5015 For example, a <file><var>package-name</var>-config</file>
5016 script or <package>pkg-config</package> configuration files.
5021 <sect id="sharedlibs-static">
5022 <heading>Static libraries</heading>
5025 The static library (<file><var>libraryname.a</var></file>)
5026 is usually provided in addition to the shared version.
5027 It is placed into the development package (see below).
5031 In some cases, it is acceptable for a library to be
5032 available in static form only; these cases include:
5034 <item>libraries for languages whose shared library support
5035 is immature or unstable</item>
5036 <item>libraries whose interfaces are in flux or under
5037 development (commonly the case when the library's
5038 major version number is zero, or where the ABI breaks
5039 across patchlevels)</item>
5040 <item>libraries which are explicitly intended to be
5041 available only in static form by their upstream
5046 <sect id="sharedlibs-dev">
5047 <heading>Development files</heading>
5050 The development files associated to a shared library need to be
5051 placed in a package called
5052 <package><var>libraryname</var><var>soversion</var>-dev</package>,
5053 or if you prefer only to support one development version at a
5054 time, <package><var>libraryname</var>-dev</package>.
5058 In case several development versions of a library exist, you may
5059 need to use <prgn>dpkg</prgn>'s Conflicts mechanism (see
5060 <ref id="conflicts">) to ensure that the user only installs one
5061 development version at a time (as different development versions are
5062 likely to have the same header files in them, which would cause a
5063 filename clash if both were installed).
5067 The development package should contain a symlink for the associated
5068 shared library without a version number. For example, the
5069 <package>libgdbm-dev</package> package should include a symlink
5070 from <file>/usr/lib/libgdbm.so</file> to
5071 <file>libgdbm.so.3.0.0</file>. This symlink is needed by the linker
5072 (<prgn>ld</prgn>) when compiling packages, as it will only look for
5073 <file>libgdbm.so</file> when compiling dynamically.
5077 <sect id="sharedlibs-intradeps">
5078 <heading>Dependencies between the packages of the same library</heading>
5081 Typically the development version should have an exact
5082 version dependency on the runtime library, to make sure that
5083 compilation and linking happens correctly. The
5084 <tt>${binary:Version}</tt> substitution variable can be
5085 useful for this purpose.
5087 Previously, <tt>${Source-Version}</tt> was used, but its name
5088 was confusing and it has been deprecated since dpkg 1.13.19.
5093 <sect id="sharedlibs-shlibdeps">
5094 <heading>Dependencies between the library and other packages -
5095 the <tt>shlibs</tt> system</heading>
5098 If a package contains a binary or library which links to a
5099 shared library, we must ensure that when the package is
5100 installed on the system, all of the libraries needed are
5101 also installed. This requirement led to the creation of the
5102 <tt>shlibs</tt> system, which is very simple in its design:
5103 any package which <em>provides</em> a shared library also
5104 provides information on the package dependencies required to
5105 ensure the presence of this library, and any package which
5106 <em>uses</em> a shared library uses this information to
5107 determine the dependencies it requires. The files which
5108 contain the mapping from shared libraries to the necessary
5109 dependency information are called <file>shlibs</file> files.
5113 Thus, when a package is built which contains any shared
5114 libraries, it must provide a <file>shlibs</file> file for other
5115 packages to use, and when a package is built which contains
5116 any shared libraries or compiled binaries, it must run
5117 <qref id="pkg-dpkg-shlibdeps"><prgn>dpkg-shlibdeps</prgn></qref>
5118 on these to determine the libraries used and hence the
5119 dependencies needed by this package.<footnote>
5121 In the past, the shared libraries linked to were
5122 determined by calling <prgn>ldd</prgn>, but now
5123 <prgn>objdump</prgn> is used to do this. The only
5124 change this makes to package building is that
5125 <prgn>dpkg-shlibdeps</prgn> must also be run on shared
5126 libraries, whereas in the past this was unnecessary.
5127 The rest of this footnote explains the advantage that
5132 We say that a binary <tt>foo</tt> <em>directly</em> uses
5133 a library <tt>libbar</tt> if it is explicitly linked
5134 with that library (that is, it uses the flag
5135 <tt>-lbar</tt> during the linking stage). Other
5136 libraries that are needed by <tt>libbar</tt> are linked
5137 <em>indirectly</em> to <tt>foo</tt>, and the dynamic
5138 linker will load them automatically when it loads
5139 <tt>libbar</tt>. A package should depend on
5140 the libraries it directly uses, and the dependencies for
5141 those libraries should automatically pull in the other
5146 Unfortunately, the <prgn>ldd</prgn> program shows both
5147 the directly and indirectly used libraries, meaning that
5148 the dependencies determined included both direct and
5149 indirect dependencies. The use of <prgn>objdump</prgn>
5150 avoids this problem by determining only the directly
5155 A good example of where this helps is the following. We
5156 could update <tt>libimlib</tt> with a new version that
5157 supports a new graphics format called dgf (but retaining
5158 the same major version number). If we used the old
5159 <prgn>ldd</prgn> method, every package that uses
5160 <tt>libimlib</tt> would need to be recompiled so it
5161 would also depend on <tt>libdgf</tt> or it wouldn't run
5162 due to missing symbols. However with the new system,
5163 packages using <tt>libimlib</tt> can rely on
5164 <tt>libimlib</tt> itself having the dependency on
5165 <tt>libdgf</tt> and so they would not need rebuilding.
5171 In the following sections, we will first describe where the
5172 various <tt>shlibs</tt> files are to be found, then how to
5173 use <prgn>dpkg-shlibdeps</prgn>, and finally the <tt>shlibs</tt>
5174 file format and how to create them if your package contains a
5179 <heading>The <tt>shlibs</tt> files present on the system</heading>
5182 There are several places where <tt>shlibs</tt> files are
5183 found. The following list gives them in the order in which
5185 <qref id="pkg-dpkg-shlibdeps"><prgn>dpkg-shlibdeps</prgn></qref>.
5186 (The first one which gives the required information is used.)
5192 <p><file>debian/shlibs.local</file></p>
5195 This lists overrides for this package. Its use is
5196 described below (see <ref id="shlibslocal">).
5201 <p><file>/etc/dpkg/shlibs.override</file></p>
5204 This lists global overrides. This list is normally
5205 empty. It is maintained by the local system
5211 <p><file>DEBIAN/shlibs</file> files in the "build directory"</p>
5214 When packages are being built, any
5215 <file>debian/shlibs</file> files are copied into the
5216 control file area of the temporary build directory and
5217 given the name <file>shlibs</file>. These files give
5218 details of any shared libraries included in the
5220 An example may help here. Let us say that the
5221 source package <tt>foo</tt> generates two binary
5222 packages, <tt>libfoo2</tt> and
5223 <tt>foo-runtime</tt>. When building the binary
5224 packages, the two packages are created in the
5225 directories <file>debian/libfoo2</file> and
5226 <file>debian/foo-runtime</file> respectively.
5227 (<file>debian/tmp</file> could be used instead of one
5228 of these.) Since <tt>libfoo2</tt> provides the
5229 <tt>libfoo</tt> shared library, it will require a
5230 <tt>shlibs</tt> file, which will be installed in
5231 <file>debian/libfoo2/DEBIAN/shlibs</file>, eventually
5233 <file>/var/lib/dpkg/info/libfoo2.shlibs</file>. Then
5234 when <prgn>dpkg-shlibdeps</prgn> is run on the
5236 <file>debian/foo-runtime/usr/bin/foo-prog</file>, it
5238 <file>debian/libfoo2/DEBIAN/shlibs</file> file to
5239 determine whether <tt>foo-prog</tt>'s library
5240 dependencies are satisfied by any of the libraries
5241 provided by <tt>libfoo2</tt>. For this reason,
5242 <prgn>dpkg-shlibdeps</prgn> must only be run once
5243 all of the individual binary packages'
5244 <tt>shlibs</tt> files have been installed into the
5251 <p><file>/var/lib/dpkg/info/*.shlibs</file></p>
5254 These are the <file>shlibs</file> files corresponding to
5255 all of the packages installed on the system, and are
5256 maintained by the relevant package maintainers.
5261 <p><file>/etc/dpkg/shlibs.default</file></p>
5264 This file lists any shared libraries whose packages
5265 have failed to provide correct <file>shlibs</file> files.
5266 It was used when the <file>shlibs</file> setup was first
5267 introduced, but it is now normally empty. It is
5268 maintained by the <tt>dpkg</tt> maintainer.
5276 <heading>How to use <prgn>dpkg-shlibdeps</prgn> and the
5277 <file>shlibs</file> files</heading>
5281 <qref id="pkg-dpkg-shlibdeps"><prgn>dpkg-shlibdeps</prgn></qref>
5282 into your <file>debian/rules</file> file. If your package
5283 contains only compiled binaries and libraries (but no scripts),
5284 you can use a command such as:
5285 <example compact="compact">
5286 dpkg-shlibdeps debian/tmp/usr/bin/* debian/tmp/usr/sbin/* \
5287 debian/tmp/usr/lib/*
5289 Otherwise, you will need to explicitly list the compiled
5290 binaries and libraries.<footnote>
5291 If you are using <tt>debhelper</tt>, the
5292 <prgn>dh_shlibdeps</prgn> program will do this work for
5293 you. It will also correctly handle multi-binary
5299 This command puts the dependency information into the
5300 <file>debian/substvars</file> file, which is then used by
5301 <prgn>dpkg-gencontrol</prgn>. You will need to place a
5302 <tt>${shlibs:Depends}</tt> variable in the <tt>Depends</tt>
5303 field in the control file for this to work.
5307 If <prgn>dpkg-shlibdeps</prgn> doesn't complain, you're
5308 done. If it does complain you might need to create your own
5309 <file>debian/shlibs.local</file> file, as explained below (see
5310 <ref id="shlibslocal">).
5314 If you have multiple binary packages, you will need to call
5315 <prgn>dpkg-shlibdeps</prgn> on each one which contains
5316 compiled libraries or binaries. In such a case, you will
5317 need to use the <tt>-T</tt> option to the <tt>dpkg</tt>
5318 utilities to specify a different <file>substvars</file> file.
5322 If you are creating a udeb for use in the Debian Installer, you
5323 will need to specify that <prgn>dpkg-shlibdeps</prgn> should use
5324 the dependency line of type <tt>udeb</tt> by adding
5325 <tt>-tudeb</tt> as option<footnote>
5326 <prgn>dh_shlibdeps</prgn> from the <tt>debhelper</tt> suite
5327 will automatically add this option if it knows it is
5329 </footnote>. If there is no dependency line of type <tt>udeb</tt>
5330 in the <file>shlibs</file> file, <prgn>dpkg-shlibdeps</prgn> will
5331 fall back to the regular dependency line.
5335 For more details on dpkg-shlibdeps, please see
5336 <ref id="pkg-dpkg-shlibdeps"> and
5337 <manref name="dpkg-shlibdeps" section="1">.
5342 <heading>The <file>shlibs</file> File Format</heading>
5345 Each <file>shlibs</file> file has the same format. Lines
5346 beginning with <tt>#</tt> are considered to be comments and
5347 are ignored. Each line is of the form:
5348 <example compact="compact">
5349 [<var>type</var>: ]<var>library-name</var> <var>soname-version</var> <var>dependencies ...</var>
5354 We will explain this by reference to the example of the
5355 <tt>zlib1g</tt> package, which (at the time of writing)
5356 installs the shared library <file>/usr/lib/libz.so.1.1.3</file>.
5360 <var>type</var> is an optional element that indicates the type
5361 of package for which the line is valid. The only type currently
5362 in use is <tt>udeb</tt>. The colon and space after the type are
5367 <var>library-name</var> is the name of the shared library,
5368 in this case <tt>libz</tt>. (This must match the name part
5369 of the soname, see below.)
5373 <var>soname-version</var> is the version part of the soname of
5374 the library. The soname is the thing that must exactly match
5375 for the library to be recognized by the dynamic linker, and is
5377 <tt><var>name</var>.so.<var>major-version</var></tt>, in our
5378 example, <tt>libz.so.1</tt>.<footnote>
5379 This can be determined using the command
5380 <example compact="compact">
5381 objdump -p /usr/lib/libz.so.1.1.3 | grep SONAME
5384 The version part is the part which comes after
5385 <tt>.so.</tt>, so in our case, it is <tt>1</tt>.
5389 <var>dependencies</var> has the same syntax as a dependency
5390 field in a binary package control file. It should give
5391 details of which packages are required to satisfy a binary
5392 built against the version of the library contained in the
5393 package. See <ref id="depsyntax"> for details.
5397 In our example, if the first version of the <tt>zlib1g</tt>
5398 package which contained a minor number of at least
5399 <tt>1.3</tt> was <var>1:1.1.3-1</var>, then the
5400 <tt>shlibs</tt> entry for this library could say:
5401 <example compact="compact">
5402 libz 1 zlib1g (>= 1:1.1.3)
5404 The version-specific dependency is to avoid warnings from
5405 the dynamic linker about using older shared libraries with
5410 As zlib1g also provides a udeb containing the shared library,
5411 there would also be a second line:
5412 <example compact="compact">
5413 udeb: libz 1 zlib1g-udeb (>= 1:1.1.3)
5419 <heading>Providing a <file>shlibs</file> file</heading>
5422 If your package provides a shared library, you need to create
5423 a <file>shlibs</file> file following the format described above.
5424 It is usual to call this file <file>debian/shlibs</file> (but if
5425 you have multiple binary packages, you might want to call it
5426 <file>debian/shlibs.<var>package</var></file> instead). Then
5427 let <file>debian/rules</file> install it in the control area:
5428 <example compact="compact">
5429 install -m644 debian/shlibs debian/tmp/DEBIAN
5431 or, in the case of a multi-binary package:
5432 <example compact="compact">
5433 install -m644 debian/shlibs.<var>package</var> debian/<var>package</var>/DEBIAN/shlibs
5435 An alternative way of doing this is to create the
5436 <file>shlibs</file> file in the control area directly from
5437 <file>debian/rules</file> without using a <file>debian/shlibs</file>
5438 file at all,<footnote>
5439 This is what <prgn>dh_makeshlibs</prgn> in the
5440 <tt>debhelper</tt> suite does. If your package also has a udeb
5441 that provides a shared library, <prgn>dh_makeshlibs</prgn> can
5442 automatically generate the <tt>udeb:</tt> lines if you specify
5443 the name of the udeb with the <tt>--add-udeb</tt> option.
5445 since the <file>debian/shlibs</file> file itself is ignored by
5446 <prgn>dpkg-shlibdeps</prgn>.
5450 As <prgn>dpkg-shlibdeps</prgn> reads the
5451 <file>DEBIAN/shlibs</file> files in all of the binary packages
5452 being built from this source package, all of the
5453 <file>DEBIAN/shlibs</file> files should be installed before
5454 <prgn>dpkg-shlibdeps</prgn> is called on any of the binary
5459 <sect1 id="shlibslocal">
5460 <heading>Writing the <file>debian/shlibs.local</file> file</heading>
5463 This file is intended only as a <em>temporary</em> fix if
5464 your binaries or libraries depend on a library whose package
5465 does not yet provide a correct <file>shlibs</file> file.
5469 We will assume that you are trying to package a binary
5470 <tt>foo</tt>. When you try running
5471 <prgn>dpkg-shlibdeps</prgn> you get the following error
5472 message (<tt>-O</tt> displays the dependency information on
5473 <tt>stdout</tt> instead of writing it to
5474 <tt>debian/substvars</tt>, and the lines have been wrapped
5475 for ease of reading):
5476 <example compact="compact">
5477 $ dpkg-shlibdeps -O debian/tmp/usr/bin/foo
5478 dpkg-shlibdeps: warning: unable to find dependency
5479 information for shared library libbar (soname 1,
5480 path /usr/lib/libbar.so.1, dependency field Depends)
5481 shlibs:Depends=libc6 (>= 2.2.2-2)
5483 You can then run <prgn>ldd</prgn> on the binary to find the
5484 full location of the library concerned:
5485 <example compact="compact">
5487 libbar.so.1 => /usr/lib/libbar.so.1 (0x4001e000)
5488 libc.so.6 => /lib/libc.so.6 (0x40032000)
5489 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
5491 So the <prgn>foo</prgn> binary depends on the
5492 <prgn>libbar</prgn> shared library, but no package seems to
5493 provide a <file>*.shlibs</file> file handling
5494 <file>libbar.so.1</file> in <file>/var/lib/dpkg/info/</file>. Let's
5495 determine the package responsible:
5496 <example compact="compact">
5497 $ dpkg -S /usr/lib/libbar.so.1
5498 bar1: /usr/lib/libbar.so.1
5499 $ dpkg -s bar1 | grep Version
5502 This tells us that the <tt>bar1</tt> package, version 1.0-1,
5503 is the one we are using. Now we can file a bug against the
5504 <tt>bar1</tt> package and create our own
5505 <file>debian/shlibs.local</file> to locally fix the problem.
5506 Including the following line into your
5507 <file>debian/shlibs.local</file> file:
5508 <example compact="compact">
5509 libbar 1 bar1 (>= 1.0-1)
5511 should allow the package build to work.
5515 As soon as the maintainer of <tt>bar1</tt> provides a
5516 correct <file>shlibs</file> file, you should remove this line
5517 from your <file>debian/shlibs.local</file> file. (You should
5518 probably also then have a versioned <tt>Build-Depends</tt>
5519 on <tt>bar1</tt> to help ensure that others do not have the
5520 same problem building your package.)
5529 <chapt id="opersys"><heading>The Operating System</heading>
5532 <heading>File system hierarchy</heading>
5536 <heading>File System Structure</heading>
5539 The location of all installed files and directories must
5540 comply with the Filesystem Hierarchy Standard (FHS),
5541 version 2.3, with the exceptions noted below, and except
5542 where doing so would violate other terms of Debian
5543 Policy. The following exceptions to the FHS apply:
5548 The optional rules related to user specific
5549 configuration files for applications are stored in
5550 the user's home directory are relaxed. It is
5551 recommended that such files start with the
5552 '<tt>.</tt>' character (a "dot file"), and if an
5553 application needs to create more than one dot file
5554 then the preferred placement is in a subdirectory
5555 with a name starting with a '.' character, (a "dot
5556 directory"). In this case it is recommended the
5557 configuration files not start with the '.'
5563 The requirement for amd64 to use <file>/lib64</file>
5564 for 64 bit binaries is removed.
5569 The requirement that
5570 <file>/usr/local/share/man</file> be "synonymous"
5571 with <file>/usr/local/man</file> is relaxed to a
5576 The requirement that windowmanagers with a single
5577 configuration file call it <file>system.*wmrc</file>
5578 is removed, as is the restriction that the window
5579 manager subdirectory be named identically to the
5580 window manager name itself.
5585 The requirement that boot manager configuration
5586 files live in <file>/etc</file>, or at least are
5587 symlinked there, is relaxed to a recommendation.
5594 The version of this document referred here can be
5595 found in the <tt>debian-policy</tt> package or on <url
5596 id="http://www.debian.org/doc/packaging-manuals/fhs/"
5597 name="FHS (Debian copy)"> alongside this manual (or, if
5598 you have the <package>debian-policy</package> installed,
5600 id="file:///usr/share/doc/debian-policy/fhs/" name="FHS
5601 (local copy)">). The
5602 latest version, which may be a more recent version, may
5604 <url id="http://www.pathname.com/fhs/" name="FHS (upstream)">.
5605 Specific questions about following the standard may be
5606 asked on the <tt>debian-devel</tt> mailing list, or
5607 referred to the FHS mailing list (see the
5608 <url id="http://www.pathname.com/fhs/" name="FHS web site"> for
5614 <heading>Site-specific programs</heading>
5617 As mandated by the FHS, packages must not place any
5618 files in <file>/usr/local</file>, either by putting them in
5619 the file system archive to be unpacked by <prgn>dpkg</prgn>
5620 or by manipulating them in their maintainer scripts.
5624 However, the package may create empty directories below
5625 <file>/usr/local</file> so that the system administrator knows
5626 where to place site-specific files. These are not
5627 directories <em>in</em> <file>/usr/local</file>, but are
5628 children of directories in <file>/usr/local</file>. These
5629 directories (<file>/usr/local/*/dir/</file>)
5630 should be removed on package removal if they are
5635 Note, that this applies only to directories <em>below</em>
5636 <file>/usr/local</file>, not <em>in</em> <file>/usr/local</file>.
5637 Packages must not create sub-directories in the directory
5638 <file>/usr/local</file> itself, except those listed in FHS,
5639 section 4.5. However, you may create directories below
5640 them as you wish. You must not remove any of the
5641 directories listed in 4.5, even if you created them.
5645 Since <file>/usr/local</file> can be mounted read-only from a
5646 remote server, these directories must be created and
5647 removed by the <prgn>postinst</prgn> and <prgn>prerm</prgn>
5648 maintainer scripts and not be included in the
5649 <file>.deb</file> archive. These scripts must not fail if
5650 either of these operations fail.
5654 For example, the <tt>emacsen-common</tt> package could
5655 contain something like
5656 <example compact="compact">
5657 if [ ! -e /usr/local/share/emacs ]
5659 if mkdir /usr/local/share/emacs 2>/dev/null
5661 chown root:staff /usr/local/share/emacs
5662 chmod 2775 /usr/local/share/emacs
5666 in its <prgn>postinst</prgn> script, and
5667 <example compact="compact">
5668 rmdir /usr/local/share/emacs/site-lisp 2>/dev/null || true
5669 rmdir /usr/local/share/emacs 2>/dev/null || true
5671 in the <prgn>prerm</prgn> script. (Note that this form is
5672 used to ensure that if the script is interrupted, the
5673 directory <file>/usr/local/share/emacs</file> will still be
5678 If you do create a directory in <file>/usr/local</file> for
5679 local additions to a package, you should ensure that
5680 settings in <file>/usr/local</file> take precedence over the
5681 equivalents in <file>/usr</file>.
5685 However, because <file>/usr/local</file> and its contents are
5686 for exclusive use of the local administrator, a package
5687 must not rely on the presence or absence of files or
5688 directories in <file>/usr/local</file> for normal operation.
5692 The <file>/usr/local</file> directory itself and all the
5693 subdirectories created by the package should (by default) have
5694 permissions 2775 (group-writable and set-group-id) and be
5695 owned by <tt>root:staff</tt>.
5700 <heading>The system-wide mail directory</heading>
5702 The system-wide mail directory is <file>/var/mail</file>. This
5703 directory is part of the base system and should not owned
5704 by any particular mail agents. The use of the old
5705 location <file>/var/spool/mail</file> is deprecated, even
5706 though the spool may still be physically located there.
5712 <heading>Users and groups</heading>
5715 <heading>Introduction</heading>
5717 The Debian system can be configured to use either plain or
5722 Some user ids (UIDs) and group ids (GIDs) are reserved
5723 globally for use by certain packages. Because some
5724 packages need to include files which are owned by these
5725 users or groups, or need the ids compiled into binaries,
5726 these ids must be used on any Debian system only for the
5727 purpose for which they are allocated. This is a serious
5728 restriction, and we should avoid getting in the way of
5729 local administration policies. In particular, many sites
5730 allocate users and/or local system groups starting at 100.
5734 Apart from this we should have dynamically allocated ids,
5735 which should by default be arranged in some sensible
5736 order, but the behavior should be configurable.
5740 Packages other than <tt>base-passwd</tt> must not modify
5741 <file>/etc/passwd</file>, <file>/etc/shadow</file>,
5742 <file>/etc/group</file> or <file>/etc/gshadow</file>.
5747 <heading>UID and GID classes</heading>
5749 The UID and GID numbers are divided into classes as
5755 Globally allocated by the Debian project, the same
5756 on every Debian system. These ids will appear in
5757 the <file>passwd</file> and <file>group</file> files of all
5758 Debian systems, new ids in this range being added
5759 automatically as the <tt>base-passwd</tt> package is
5764 Packages which need a single statically allocated
5765 uid or gid should use one of these; their
5766 maintainers should ask the <tt>base-passwd</tt>
5774 Dynamically allocated system users and groups.
5775 Packages which need a user or group, but can have
5776 this user or group allocated dynamically and
5777 differently on each system, should use <tt>adduser
5778 --system</tt> to create the group and/or user.
5779 <prgn>adduser</prgn> will check for the existence of
5780 the user or group, and if necessary choose an unused
5781 id based on the ranges specified in
5782 <file>adduser.conf</file>.
5786 <tag>1000-29999:</tag>
5789 Dynamically allocated user accounts. By default
5790 <prgn>adduser</prgn> will choose UIDs and GIDs for
5791 user accounts in this range, though
5792 <file>adduser.conf</file> may be used to modify this
5797 <tag>30000-59999:</tag>
5802 <tag>60000-64999:</tag>
5805 Globally allocated by the Debian project, but only
5806 created on demand. The ids are allocated centrally
5807 and statically, but the actual accounts are only
5808 created on users' systems on demand.
5812 These ids are for packages which are obscure or
5813 which require many statically-allocated ids. These
5814 packages should check for and create the accounts in
5815 <file>/etc/passwd</file> or <file>/etc/group</file> (using
5816 <prgn>adduser</prgn> if it has this facility) if
5817 necessary. Packages which are likely to require
5818 further allocations should have a "hole" left after
5819 them in the allocation, to give them room to
5824 <tag>65000-65533:</tag>
5832 User <tt>nobody</tt>. The corresponding gid refers
5833 to the group <tt>nogroup</tt>.
5840 <tt>(uid_t)(-1) == (gid_t)(-1)</tt> <em>must
5841 not</em> be used, because it is the error return
5850 <sect id="sysvinit">
5851 <heading>System run levels and <file>init.d</file> scripts</heading>
5853 <sect1 id="/etc/init.d">
5854 <heading>Introduction</heading>
5857 The <file>/etc/init.d</file> directory contains the scripts
5858 executed by <prgn>init</prgn> at boot time and when the
5859 init state (or "runlevel") is changed (see <manref
5860 name="init" section="8">).
5864 There are at least two different, yet functionally
5865 equivalent, ways of handling these scripts. For the sake
5866 of simplicity, this document describes only the symbolic
5867 link method. However, it must not be assumed by maintainer
5868 scripts that this method is being used, and any automated
5869 manipulation of the various runlevel behaviors by
5870 maintainer scripts must be performed using
5871 <prgn>update-rc.d</prgn> as described below and not by
5872 manually installing or removing symlinks. For information
5873 on the implementation details of the other method,
5874 implemented in the <tt>file-rc</tt> package, please refer
5875 to the documentation of that package.
5879 These scripts are referenced by symbolic links in the
5880 <file>/etc/rc<var>n</var>.d</file> directories. When changing
5881 runlevels, <prgn>init</prgn> looks in the directory
5882 <file>/etc/rc<var>n</var>.d</file> for the scripts it should
5883 execute, where <tt><var>n</var></tt> is the runlevel that
5884 is being changed to, or <tt>S</tt> for the boot-up
5889 The names of the links all have the form
5890 <file>S<var>mm</var><var>script</var></file> or
5891 <file>K<var>mm</var><var>script</var></file> where
5892 <var>mm</var> is a two-digit number and <var>script</var>
5893 is the name of the script (this should be the same as the
5894 name of the actual script in <file>/etc/init.d</file>).
5898 When <prgn>init</prgn> changes runlevel first the targets
5899 of the links whose names start with a <tt>K</tt> are
5900 executed, each with the single argument <tt>stop</tt>,
5901 followed by the scripts prefixed with an <tt>S</tt>, each
5902 with the single argument <tt>start</tt>. (The links are
5903 those in the <file>/etc/rc<var>n</var>.d</file> directory
5904 corresponding to the new runlevel.) The <tt>K</tt> links
5905 are responsible for killing services and the <tt>S</tt>
5906 link for starting services upon entering the runlevel.
5910 For example, if we are changing from runlevel 2 to
5911 runlevel 3, init will first execute all of the <tt>K</tt>
5912 prefixed scripts it finds in <file>/etc/rc3.d</file>, and then
5913 all of the <tt>S</tt> prefixed scripts in that directory.
5914 The links starting with <tt>K</tt> will cause the
5915 referred-to file to be executed with an argument of
5916 <tt>stop</tt>, and the <tt>S</tt> links with an argument
5921 The two-digit number <var>mm</var> is used to determine
5922 the order in which to run the scripts: low-numbered links
5923 have their scripts run first. For example, the
5924 <tt>K20</tt> scripts will be executed before the
5925 <tt>K30</tt> scripts. This is used when a certain service
5926 must be started before another. For example, the name
5927 server <prgn>bind</prgn> might need to be started before
5928 the news server <prgn>inn</prgn> so that <prgn>inn</prgn>
5929 can set up its access lists. In this case, the script
5930 that starts <prgn>bind</prgn> would have a lower number
5931 than the script that starts <prgn>inn</prgn> so that it
5933 <example compact="compact">
5940 The two runlevels 0 (halt) and 6 (reboot) are slightly
5941 different. In these runlevels, the links with an
5942 <tt>S</tt> prefix are still called after those with a
5943 <tt>K</tt> prefix, but they too are called with the single
5944 argument <tt>stop</tt>.
5949 <heading>Writing the scripts</heading>
5952 Packages that include daemons for system services should
5953 place scripts in <file>/etc/init.d</file> to start or stop
5954 services at boot time or during a change of runlevel.
5955 These scripts should be named
5956 <file>/etc/init.d/<var>package</var></file>, and they should
5957 accept one argument, saying what to do:
5960 <tag><tt>start</tt></tag>
5961 <item>start the service,</item>
5963 <tag><tt>stop</tt></tag>
5964 <item>stop the service,</item>
5966 <tag><tt>restart</tt></tag>
5967 <item>stop and restart the service if it's already running,
5968 otherwise start the service</item>
5970 <tag><tt>reload</tt></tag>
5971 <item><p>cause the configuration of the service to be
5972 reloaded without actually stopping and restarting
5975 <tag><tt>force-reload</tt></tag>
5976 <item>cause the configuration to be reloaded if the
5977 service supports this, otherwise restart the
5981 The <tt>start</tt>, <tt>stop</tt>, <tt>restart</tt>, and
5982 <tt>force-reload</tt> options should be supported by all
5983 scripts in <file>/etc/init.d</file>, the <tt>reload</tt>
5988 The <file>init.d</file> scripts must ensure that they will
5989 behave sensibly (i.e., returning success and not starting
5990 multiple copies of a service) if invoked with <tt>start</tt>
5991 when the service is already running, or with <tt>stop</tt>
5992 when it isn't, and that they don't kill unfortunately-named
5993 user processes. The best way to achieve this is usually to
5994 use <prgn>start-stop-daemon</prgn> with the <tt>--oknodo</tt>
5999 If a service reloads its configuration automatically (as
6000 in the case of <prgn>cron</prgn>, for example), the
6001 <tt>reload</tt> option of the <file>init.d</file> script
6002 should behave as if the configuration has been reloaded
6007 The <file>/etc/init.d</file> scripts must be treated as
6008 configuration files, either (if they are present in the
6009 package, that is, in the .deb file) by marking them as
6010 <tt>conffile</tt>s, or, (if they do not exist in the .deb)
6011 by managing them correctly in the maintainer scripts (see
6012 <ref id="config-files">). This is important since we want
6013 to give the local system administrator the chance to adapt
6014 the scripts to the local system, e.g., to disable a
6015 service without de-installing the package, or to specify
6016 some special command line options when starting a service,
6017 while making sure their changes aren't lost during the next
6022 These scripts should not fail obscurely when the
6023 configuration files remain but the package has been
6024 removed, as configuration files remain on the system after
6025 the package has been removed. Only when <prgn>dpkg</prgn>
6026 is executed with the <tt>--purge</tt> option will
6027 configuration files be removed. In particular, as the
6028 <file>/etc/init.d/<var>package</var></file> script itself is
6029 usually a <tt>conffile</tt>, it will remain on the system
6030 if the package is removed but not purged. Therefore, you
6031 should include a <tt>test</tt> statement at the top of the
6033 <example compact="compact">
6034 test -f <var>program-executed-later-in-script</var> || exit 0
6039 Often there are some variables in the <file>init.d</file>
6040 scripts whose values control the behavior of the scripts,
6041 and which a system administrator is likely to want to
6042 change. As the scripts themselves are frequently
6043 <tt>conffile</tt>s, modifying them requires that the
6044 administrator merge in their changes each time the package
6045 is upgraded and the <tt>conffile</tt> changes. To ease
6046 the burden on the system administrator, such configurable
6047 values should not be placed directly in the script.
6048 Instead, they should be placed in a file in
6049 <file>/etc/default</file>, which typically will have the same
6050 base name as the <file>init.d</file> script. This extra file
6051 should be sourced by the script when the script runs. It
6052 must contain only variable settings and comments in SUSv3
6053 <prgn>sh</prgn> format. It may either be a
6054 <tt>conffile</tt> or a configuration file maintained by
6055 the package maintainer scripts. See <ref id="config-files">
6060 To ensure that vital configurable values are always
6061 available, the <file>init.d</file> script should set default
6062 values for each of the shell variables it uses, either
6063 before sourcing the <file>/etc/default/</file> file or
6064 afterwards using something like the <tt>:
6065 ${VAR:=default}</tt> syntax. Also, the <file>init.d</file>
6066 script must behave sensibly and not fail if the
6067 <file>/etc/default</file> file is deleted.
6071 <file>/var/run</file> and <file>/var/lock</file> may be mounted
6072 as temporary filesystems<footnote>
6073 For example, using the <tt>RAMRUN</tt> and <tt>RAMLOCK</tt>
6074 options in <file>/etc/default/rcS</file>.
6075 </footnote>, so the <file>init.d</file> scripts must handle this
6076 correctly. This will typically amount to creating any required
6077 subdirectories dynamically when the <file>init.d</file> script
6078 is run, rather than including them in the package and relying on
6079 <prgn>dpkg</prgn> to create them.
6084 <heading>Interfacing with the initscript system</heading>
6087 Maintainers should use the abstraction layer provided by
6088 the <prgn>update-rc.d</prgn> and <prgn>invoke-rc.d</prgn>
6089 programs to deal with initscripts in their packages'
6090 scripts such as <prgn>postinst</prgn>, <prgn>prerm</prgn>
6091 and <prgn>postrm</prgn>.
6095 Directly managing the /etc/rc?.d links and directly
6096 invoking the <file>/etc/init.d/</file> initscripts should
6097 be done only by packages providing the initscript
6098 subsystem (such as <prgn>sysv-rc</prgn> and
6099 <prgn>file-rc</prgn>).
6103 <heading>Managing the links</heading>
6106 The program <prgn>update-rc.d</prgn> is provided for
6107 package maintainers to arrange for the proper creation and
6108 removal of <file>/etc/rc<var>n</var>.d</file> symbolic links,
6109 or their functional equivalent if another method is being
6110 used. This may be used by maintainers in their packages'
6111 <prgn>postinst</prgn> and <prgn>postrm</prgn> scripts.
6115 You must not include any <file>/etc/rc<var>n</var>.d</file>
6116 symbolic links in the actual archive or manually create or
6117 remove the symbolic links in maintainer scripts; you must
6118 use the <prgn>update-rc.d</prgn> program instead. (The
6119 former will fail if an alternative method of maintaining
6120 runlevel information is being used.) You must not include
6121 the <file>/etc/rc<var>n</var>.d</file> directories themselves
6122 in the archive either. (Only the <tt>sysvinit</tt>
6127 By default <prgn>update-rc.d</prgn> will start services in
6128 each of the multi-user state runlevels (2, 3, 4, and 5)
6129 and stop them in the halt runlevel (0), the single-user
6130 runlevel (1) and the reboot runlevel (6). The system
6131 administrator will have the opportunity to customize
6132 runlevels by simply adding, moving, or removing the
6133 symbolic links in <file>/etc/rc<var>n</var>.d</file> if
6134 symbolic links are being used, or by modifying
6135 <file>/etc/runlevel.conf</file> if the <tt>file-rc</tt> method
6140 To get the default behavior for your package, put in your
6141 <prgn>postinst</prgn> script
6142 <example compact="compact">
6143 update-rc.d <var>package</var> defaults
6145 and in your <prgn>postrm</prgn>
6146 <example compact="compact">
6147 if [ "$1" = purge ]; then
6148 update-rc.d <var>package</var> remove
6150 </example>. Note that if your package changes runlevels
6151 or priority, you may have to remove and recreate the links,
6152 since otherwise the old links may persist. Refer to the
6153 documentation of <prgn>update-rc.d</prgn>.
6157 This will use a default sequence number of 20. If it does
6158 not matter when or in which order the <file>init.d</file>
6159 script is run, use this default. If it does, then you
6160 should talk to the maintainer of the <prgn>sysvinit</prgn>
6161 package or post to <tt>debian-devel</tt>, and they will
6162 help you choose a number.
6166 For more information about using <tt>update-rc.d</tt>,
6167 please consult its man page <manref name="update-rc.d"
6173 <heading>Running initscripts</heading>
6175 The program <prgn>invoke-rc.d</prgn> is provided to make
6176 it easier for package maintainers to properly invoke an
6177 initscript, obeying runlevel and other locally-defined
6178 constraints that might limit a package's right to start,
6179 stop and otherwise manage services. This program may be
6180 used by maintainers in their packages' scripts.
6184 The package maintainer scripts must use
6185 <prgn>invoke-rc.d</prgn> to invoke the
6186 <file>/etc/init.d/*</file> initscripts, instead of
6187 calling them directly.
6191 By default, <prgn>invoke-rc.d</prgn> will pass any
6192 action requests (start, stop, reload, restart...) to the
6193 <file>/etc/init.d</file> script, filtering out requests
6194 to start or restart a service out of its intended
6199 Most packages will simply need to change:
6200 <example compact="compact">/etc/init.d/<package>
6201 <action></example> in their <prgn>postinst</prgn>
6202 and <prgn>prerm</prgn> scripts to:
6203 <example compact="compact">
6204 if which invoke-rc.d >/dev/null 2>&1; then
6205 invoke-rc.d <var>package</var> <action>
6207 /etc/init.d/<var>package</var> <action>
6213 A package should register its initscript services using
6214 <prgn>update-rc.d</prgn> before it tries to invoke them
6215 using <prgn>invoke-rc.d</prgn>. Invocation of
6216 unregistered services may fail.
6220 For more information about using
6221 <prgn>invoke-rc.d</prgn>, please consult its man page
6222 <manref name="invoke-rc.d" section="8">.
6228 <heading>Boot-time initialization</heading>
6231 There used to be another directory, <file>/etc/rc.boot</file>,
6232 which contained scripts which were run once per machine
6233 boot. This has been deprecated in favour of links from
6234 <file>/etc/rcS.d</file> to files in <file>/etc/init.d</file> as
6235 described in <ref id="/etc/init.d">. Packages must not
6236 place files in <file>/etc/rc.boot</file>.
6241 <heading>Example</heading>
6244 An example on which you can base your
6245 <file>/etc/init.d</file> scripts is found in
6246 <file>/etc/init.d/skeleton</file>.
6253 <heading>Console messages from <file>init.d</file> scripts</heading>
6256 This section describes the formats to be used for messages
6257 written to standard output by the <file>/etc/init.d</file>
6258 scripts. The intent is to improve the consistency of
6259 Debian's startup and shutdown look and feel. For this
6260 reason, please look very carefully at the details. We want
6261 the messages to have the same format in terms of wording,
6262 spaces, punctuation and case of letters.
6266 Here is a list of overall rules that should be used for
6267 messages generated by <file>/etc/init.d</file> scripts.
6273 The message should fit in one line (fewer than 80
6274 characters), start with a capital letter and end with
6275 a period (<tt>.</tt>) and line feed (<tt>"\n"</tt>).
6279 If the script is performing some time consuming task in
6280 the background (not merely starting or stopping a
6281 program, for instance), an ellipsis (three dots:
6282 <tt>...</tt>) should be output to the screen, with no
6283 leading or tailing whitespace or line feeds.
6287 The messages should appear as if the computer is telling
6288 the user what it is doing (politely :-), but should not
6289 mention "it" directly. For example, instead of:
6290 <example compact="compact">
6291 I'm starting network daemons: nfsd mountd.
6293 the message should say
6294 <example compact="compact">
6295 Starting network daemons: nfsd mountd.
6302 <tt>init.d</tt> script should use the following standard
6303 message formats for the situations enumerated below.
6309 <p>When daemons are started</p>
6312 If the script starts one or more daemons, the output
6313 should look like this (a single line, no leading
6315 <example compact="compact">
6316 Starting <var>description</var>: <var>daemon-1</var> ... <var>daemon-n</var>.
6318 The <var>description</var> should describe the
6319 subsystem the daemon or set of daemons are part of,
6320 while <var>daemon-1</var> up to <var>daemon-n</var>
6321 denote each daemon's name (typically the file name of
6326 For example, the output of <file>/etc/init.d/lpd</file>
6328 <example compact="compact">
6329 Starting printer spooler: lpd.
6334 This can be achieved by saying
6335 <example compact="compact">
6336 echo -n "Starting printer spooler: lpd"
6337 start-stop-daemon --start --quiet --exec /usr/sbin/lpd
6340 in the script. If there are more than one daemon to
6341 start, the output should look like this:
6342 <example compact="compact">
6343 echo -n "Starting remote file system services:"
6344 echo -n " nfsd"; start-stop-daemon --start --quiet nfsd
6345 echo -n " mountd"; start-stop-daemon --start --quiet mountd
6346 echo -n " ugidd"; start-stop-daemon --start --quiet ugidd
6349 This makes it possible for the user to see what is
6350 happening and when the final daemon has been started.
6351 Care should be taken in the placement of white spaces:
6352 in the example above the system administrators can
6353 easily comment out a line if they don't want to start
6354 a specific daemon, while the displayed message still
6360 <p>When a system parameter is being set</p>
6363 If you have to set up different system parameters
6364 during the system boot, you should use this format:
6365 <example compact="compact">
6366 Setting <var>parameter</var> to "<var>value</var>".
6371 You can use a statement such as the following to get
6373 <example compact="compact">
6374 echo "Setting DNS domainname to \"$domainname\"."
6379 Note that the same symbol (<tt>"</tt>) is used for the left
6380 and right quotation marks. A grave accent (<tt>`</tt>) is
6381 not a quote character; neither is an apostrophe
6387 <p>When a daemon is stopped or restarted</p>
6390 When you stop or restart a daemon, you should issue a
6391 message identical to the startup message, except that
6392 <tt>Starting</tt> is replaced with <tt>Stopping</tt>
6393 or <tt>Restarting</tt> respectively.
6397 For example, stopping the printer daemon will look like
6399 <example compact="compact">
6400 Stopping printer spooler: lpd.
6406 <p>When something is executed</p>
6409 There are several examples where you have to run a
6410 program at system startup or shutdown to perform a
6411 specific task, for example, setting the system's clock
6412 using <prgn>netdate</prgn> or killing all processes
6413 when the system shuts down. Your message should look
6415 <example compact="compact">
6416 Doing something very useful...done.
6418 You should print the <tt>done.</tt> immediately after
6419 the job has been completed, so that the user is
6420 informed why they have to wait. You can get this
6422 <example compact="compact">
6423 echo -n "Doing something very useful..."
6432 <p>When the configuration is reloaded</p>
6435 When a daemon is forced to reload its configuration
6436 files you should use the following format:
6437 <example compact="compact">
6438 Reloading <var>description</var> configuration...done.
6440 where <var>description</var> is the same as in the
6441 daemon starting message.
6449 <heading>Cron jobs</heading>
6452 Packages must not modify the configuration file
6453 <file>/etc/crontab</file>, and they must not modify the files in
6454 <file>/var/spool/cron/crontabs</file>.</p>
6457 If a package wants to install a job that has to be executed
6458 via cron, it should place a file with the name of the
6459 package in one or more of the following directories:
6460 <example compact="compact">
6466 As these directory names imply, the files within them are
6467 executed on an hourly, daily, weekly, or monthly basis,
6468 respectively. The exact times are listed in
6469 <file>/etc/crontab</file>.</p>
6472 All files installed in any of these directories must be
6473 scripts (e.g., shell scripts or Perl scripts) so that they
6474 can easily be modified by the local system administrator.
6475 In addition, they must be treated as configuration files.
6479 If a certain job has to be executed at some other frequency or
6480 at a specific time, the package should install a file
6481 <file>/etc/cron.d/<var>package</var></file>. This file uses the
6482 same syntax as <file>/etc/crontab</file> and is processed by
6483 <prgn>cron</prgn> automatically. The file must also be
6484 treated as a configuration file. (Note that entries in the
6485 <file>/etc/cron.d</file> directory are not handled by
6486 <prgn>anacron</prgn>. Thus, you should only use this
6487 directory for jobs which may be skipped if the system is not
6491 The scripts or crontab entries in these directories should
6492 check if all necessary programs are installed before they
6493 try to execute them. Otherwise, problems will arise when a
6494 package was removed but not purged since configuration files
6495 are kept on the system in this situation.</p>
6499 <heading>Menus</heading>
6502 The Debian <tt>menu</tt> package provides a standard
6503 interface between packages providing applications and
6504 <em>menu programs</em> (either X window managers or
6505 text-based menu programs such as <prgn>pdmenu</prgn>).
6509 All packages that provide applications that need not be
6510 passed any special command line arguments for normal
6511 operation should register a menu entry for those
6512 applications, so that users of the <tt>menu</tt> package
6513 will automatically get menu entries in their window
6514 managers, as well in shells like <tt>pdmenu</tt>.
6518 Menu entries should follow the current menu policy.
6522 The menu policy can be found in the <tt>menu-policy</tt>
6523 files in the <tt>debian-policy</tt> package.
6524 It is also available from the Debian web mirrors at
6525 <tt><url name="/doc/packaging-manuals/menu-policy/"
6526 id="http://www.debian.org/doc/packaging-manuals/menu-policy/"></tt>.
6530 Please also refer to the <em>Debian Menu System</em>
6531 documentation that comes with the <package>menu</package>
6532 package for information about how to register your
6538 <heading>Multimedia handlers</heading>
6541 MIME (Multipurpose Internet Mail Extensions, RFCs 2045-2049)
6542 is a mechanism for encoding files and data streams and
6543 providing meta-information about them, in particular their
6544 type (e.g. audio or video) and format (e.g. PNG, HTML,
6549 Registration of MIME type handlers allows programs like mail
6550 user agents and web browsers to invoke these handlers to
6551 view, edit or display MIME types they don't support directly.
6555 Packages which provide the ability to view/show/play,
6556 compose, edit or print MIME types should register themselves
6557 as such following the current MIME support policy.
6561 The MIME support policy can be found in the <tt>mime-policy</tt>
6562 files in the <tt>debian-policy</tt> package.
6563 It is also available from the Debian web mirrors at
6564 <tt><url name="/doc/packaging-manuals/mime-policy/"
6565 id="http://www.debian.org/doc/packaging-manuals/mime-policy/"></tt>.
6571 <heading>Keyboard configuration</heading>
6574 To achieve a consistent keyboard configuration so that all
6575 applications interpret a keyboard event the same way, all
6576 programs in the Debian distribution must be configured to
6577 comply with the following guidelines.
6581 The following keys must have the specified interpretations:
6584 <tag><tt><--</tt></tag>
6585 <item>delete the character to the left of the cursor</item>
6587 <tag><tt>Delete</tt></tag>
6588 <item>delete the character to the right of the cursor</item>
6590 <tag><tt>Control+H</tt></tag>
6591 <item>emacs: the help prefix</item>
6594 The interpretation of any keyboard events should be
6595 independent of the terminal that is used, be it a virtual
6596 console, an X terminal emulator, an rlogin/telnet session,
6601 The following list explains how the different programs
6602 should be set up to achieve this:
6608 <tt><--</tt> generates <tt>KB_BackSpace</tt> in X.
6612 <tt>Delete</tt> generates <tt>KB_Delete</tt> in X.
6616 X translations are set up to make
6617 <tt>KB_Backspace</tt> generate ASCII DEL, and to make
6618 <tt>KB_Delete</tt> generate <tt>ESC [ 3 ~</tt> (this
6619 is the vt220 escape code for the "delete character"
6620 key). This must be done by loading the X resources
6621 using <prgn>xrdb</prgn> on all local X displays, not
6622 using the application defaults, so that the
6623 translation resources used correspond to the
6624 <prgn>xmodmap</prgn> settings.
6628 The Linux console is configured to make
6629 <tt><--</tt> generate DEL, and <tt>Delete</tt>
6630 generate <tt>ESC [ 3 ~</tt>.
6634 X applications are configured so that <tt><</tt>
6635 deletes left, and <tt>Delete</tt> deletes right. Motif
6636 applications already work like this.
6640 Terminals should have <tt>stty erase ^?</tt> .
6644 The <tt>xterm</tt> terminfo entry should have <tt>ESC
6645 [ 3 ~</tt> for <tt>kdch1</tt>, just as for
6646 <tt>TERM=linux</tt> and <tt>TERM=vt220</tt>.
6650 Emacs is programmed to map <tt>KB_Backspace</tt> or
6651 the <tt>stty erase</tt> character to
6652 <tt>delete-backward-char</tt>, and <tt>KB_Delete</tt>
6653 or <tt>kdch1</tt> to <tt>delete-forward-char</tt>, and
6654 <tt>^H</tt> to <tt>help</tt> as always.
6658 Other applications use the <tt>stty erase</tt>
6659 character and <tt>kdch1</tt> for the two delete keys,
6660 with ASCII DEL being "delete previous character" and
6661 <tt>kdch1</tt> being "delete character under
6669 This will solve the problem except for the following
6676 Some terminals have a <tt><--</tt> key that cannot
6677 be made to produce anything except <tt>^H</tt>. On
6678 these terminals Emacs help will be unavailable on
6679 <tt>^H</tt> (assuming that the <tt>stty erase</tt>
6680 character takes precedence in Emacs, and has been set
6681 correctly). <tt>M-x help</tt> or <tt>F1</tt> (if
6682 available) can be used instead.
6686 Some operating systems use <tt>^H</tt> for <tt>stty
6687 erase</tt>. However, modern telnet versions and all
6688 rlogin versions propagate <tt>stty</tt> settings, and
6689 almost all UNIX versions honour <tt>stty erase</tt>.
6690 Where the <tt>stty</tt> settings are not propagated
6691 correctly, things can be made to work by using
6692 <tt>stty</tt> manually.
6696 Some systems (including previous Debian versions) use
6697 <prgn>xmodmap</prgn> to arrange for both
6698 <tt><--</tt> and <tt>Delete</tt> to generate
6699 <tt>KB_Delete</tt>. We can change the behavior of
6700 their X clients using the same X resources that we use
6701 to do it for our own clients, or configure our clients
6702 using their resources when things are the other way
6703 around. On displays configured like this
6704 <tt>Delete</tt> will not work, but <tt><--</tt>
6709 Some operating systems have different <tt>kdch1</tt>
6710 settings in their <tt>terminfo</tt> database for
6711 <tt>xterm</tt> and others. On these systems the
6712 <tt>Delete</tt> key will not work correctly when you
6713 log in from a system conforming to our policy, but
6714 <tt><--</tt> will.
6721 <heading>Environment variables</heading>
6724 A program must not depend on environment variables to get
6725 reasonable defaults. (That's because these environment
6726 variables would have to be set in a system-wide
6727 configuration file like <file>/etc/profile</file>, which is not
6728 supported by all shells.)
6732 If a program usually depends on environment variables for its
6733 configuration, the program should be changed to fall back to
6734 a reasonable default configuration if these environment
6735 variables are not present. If this cannot be done easily
6736 (e.g., if the source code of a non-free program is not
6737 available), the program must be replaced by a small
6738 "wrapper" shell script which sets the environment variables
6739 if they are not already defined, and calls the original program.
6743 Here is an example of a wrapper script for this purpose:
6745 <example compact="compact">
6747 BAR=${BAR:-/var/lib/fubar}
6749 exec /usr/lib/foo/foo "$@"
6754 Furthermore, as <file>/etc/profile</file> is a configuration
6755 file of the <prgn>base-files</prgn> package, other packages must
6756 not put any environment variables or other commands into that
6761 <sect id="doc-base">
6762 <heading>Registering Documents using doc-base</heading>
6765 The <package>doc-base</package> package implements a
6766 flexible mechanism for handling and presenting
6767 documentation. The recommended practice is for every Debian
6768 package that provides online documentation (other than just
6769 manual pages) to register these documents with
6770 <package>doc-base</package> by installing a
6771 <package>doc-base</package> control file via the
6772 <prgn/install-docs/ script at installation time and
6773 de-register the manuals again when the package is removed.
6776 Please refer to the documentation that comes with the
6777 <package>doc-base</package> package for information and
6786 <heading>Files</heading>
6789 <heading>Binaries</heading>
6792 Two different packages must not install programs with
6793 different functionality but with the same filenames. (The
6794 case of two programs having the same functionality but
6795 different implementations is handled via "alternatives" or
6796 the "Conflicts" mechanism. See <ref id="maintscripts"> and
6797 <ref id="conflicts"> respectively.) If this case happens,
6798 one of the programs must be renamed. The maintainers should
6799 report this to the <tt>debian-devel</tt> mailing list and
6800 try to find a consensus about which program will have to be
6801 renamed. If a consensus cannot be reached, <em>both</em>
6802 programs must be renamed.
6806 By default, when a package is being built, any binaries
6807 created should include debugging information, as well as
6808 being compiled with optimization. You should also turn on
6809 as many reasonable compilation warnings as possible; this
6810 makes life easier for porters, who can then look at build
6811 logs for possible problems. For the C programming language,
6812 this means the following compilation parameters should be
6814 <example compact="compact">
6816 CFLAGS = -O2 -g -Wall # sane warning options vary between programs
6818 INSTALL = install -s # (or use strip on the files in debian/tmp)
6823 Note that by default all installed binaries should be stripped,
6824 either by using the <tt>-s</tt> flag to
6825 <prgn>install</prgn>, or by calling <prgn>strip</prgn> on
6826 the binaries after they have been copied into
6827 <file>debian/tmp</file> but before the tree is made into a
6832 Although binaries in the build tree should be compiled with
6833 debugging information by default, it can often be difficult to
6834 debug programs if they are also subjected to compiler
6835 optimization. For this reason, it is recommended to support the
6836 standardized environment variable <tt>DEB_BUILD_OPTIONS</tt>
6837 (see <ref id="debianrules-options">). This variable can contain
6838 several flags to change how a package is compiled and built.
6842 It is up to the package maintainer to decide what
6843 compilation options are best for the package. Certain
6844 binaries (such as computationally-intensive programs) will
6845 function better with certain flags (<tt>-O3</tt>, for
6846 example); feel free to use them. Please use good judgment
6847 here. Don't use flags for the sake of it; only use them
6848 if there is good reason to do so. Feel free to override
6849 the upstream author's ideas about which compilation
6850 options are best: they are often inappropriate for our
6856 <sect id="libraries">
6857 <heading>Libraries</heading>
6860 If the package is <strong>architecture: any</strong>, then
6861 the shared library compilation and linking flags must have
6862 <tt>-fPIC</tt>, or the package shall not build on some of
6863 the supported architectures<footnote>
6865 If you are using GCC, <tt>-fPIC</tt> produces code with
6866 relocatable position independent code, which is required for
6867 most architectures to create a shared library, with i386 and
6868 perhaps some others where non position independent code is
6869 permitted in a shared library.
6872 Position independent code may have a performance penalty,
6873 especially on <tt>i386</tt>. However, in most cases the
6874 speed penalty must be measured against the memory wasted on
6875 the few architectures where non position independent code is
6878 </footnote>. Any exception to this rule must be discussed on
6879 the mailing list <em>debian-devel@lists.debian.org</em>, and
6880 a rough consensus obtained. The reasons for not compiling
6881 with <tt>-fPIC</tt> flag must be recorded in the file
6882 <tt>README.Debian</tt>, and care must be taken to either
6883 restrict the architecture or arrange for <tt>-fPIC</tt> to
6884 be used on architectures where it is required.<footnote>
6886 Some of the reasons why this might be required is if the
6887 library contains hand crafted assembly code that is not
6888 relocatable, the speed penalty is excessive for compute
6889 intensive libs, and similar reasons.
6894 As to the static libraries, the common case is not to have
6895 relocatable code, since there is no benefit, unless in specific
6896 cases; therefore the static version must not be compiled
6897 with the <tt>-fPIC</tt> flag. Any exception to this rule
6898 should be discussed on the mailing list
6899 <em>debian-devel@lists.debian.org</em>, and the reasons for
6900 compiling with the <tt>-fPIC</tt> flag must be recorded in
6901 the file <tt>README.Debian</tt>. <footnote>
6903 Some of the reasons for linking static libraries with
6904 the <tt>-fPIC</tt> flag are if, for example, one needs a
6905 Perl API for a library that is under rapid development,
6906 and has an unstable API, so shared libraries are
6907 pointless at this phase of the library's development. In
6908 that case, since Perl needs a library with relocatable
6909 code, it may make sense to create a static library with
6910 relocatable code. Another reason cited is if you are
6911 distilling various libraries into a common shared
6912 library, like <tt>mklibs</tt> does in the Debian
6918 In other words, if both a shared and a static library is
6919 being built, each source unit (<tt>*.c</tt>, for example,
6920 for C files) will need to be compiled twice, for the normal
6924 You must specify the gcc option <tt>-D_REENTRANT</tt>
6925 when building a library (either static or shared) to make
6926 the library compatible with LinuxThreads.
6930 Although not enforced by the build tools, shared libraries
6931 must be linked against all libraries that they use symbols from
6932 in the same way that binaries are. This ensures the correct
6933 functioning of the <qref id="sharedlibs-shlibdeps">shlibs</qref>
6934 system and guarantees that all libraries can be safely opened
6935 with <tt>dlopen()</tt>. Packagers may wish to use the gcc
6936 option <tt>-Wl,-z,defs</tt> when building a shared library.
6937 Since this option enforces symbol resolution at build time,
6938 a missing library reference will be caught early as a fatal
6943 All installed shared libraries should be stripped with
6944 <example compact="compact">
6945 strip --strip-unneeded <var>your-lib</var>
6947 (The option <tt>--strip-unneeded</tt> makes
6948 <prgn>strip</prgn> remove only the symbols which aren't
6949 needed for relocation processing.) Shared libraries can
6950 function perfectly well when stripped, since the symbols for
6951 dynamic linking are in a separate part of the ELF object
6953 You might also want to use the options
6954 <tt>--remove-section=.comment</tt> and
6955 <tt>--remove-section=.note</tt> on both shared libraries
6956 and executables, and <tt>--strip-debug</tt> on static
6962 Note that under some circumstances it may be useful to
6963 install a shared library unstripped, for example when
6964 building a separate package to support debugging.
6968 Shared object files (often <file>.so</file> files) that are not
6969 public libraries, that is, they are not meant to be linked
6970 to by third party executables (binaries of other packages),
6971 should be installed in subdirectories of the
6972 <file>/usr/lib</file> directory. Such files are exempt from the
6973 rules that govern ordinary shared libraries, except that
6974 they must not be installed executable and should be
6976 A common example are the so-called "plug-ins",
6977 internal shared objects that are dynamically loaded by
6978 programs using <manref name="dlopen" section="3">.
6983 Packages containing shared libraries that may be linked to
6984 by other packages' binaries, but which for some
6985 <em>compelling</em> reason can not be installed in
6986 <file>/usr/lib</file> directory, may install the shared library
6987 files in subdirectories of the <file>/usr/lib</file> directory,
6988 in which case they should arrange to add that directory in
6989 <file>/etc/ld.so.conf</file> in the package's post-installation
6990 script, and remove it in the package's post-removal script.
6994 An ever increasing number of packages are using
6995 <prgn>libtool</prgn> to do their linking. The latest GNU
6996 libtools (>= 1.3a) can take advantage of the metadata in the
6997 installed <prgn>libtool</prgn> archive files (<file>*.la</file>
6998 files). The main advantage of <prgn>libtool</prgn>'s
6999 <file>.la</file> files is that it allows <prgn>libtool</prgn> to
7000 store and subsequently access metadata with respect to the
7001 libraries it builds. <prgn>libtool</prgn> will search for
7002 those files, which contain a lot of useful information about
7003 a library (such as library dependency information for static
7004 linking). Also, they're <em>essential</em> for programs
7005 using <tt>libltdl</tt>.<footnote>
7006 Although <prgn>libtool</prgn> is fully capable of
7007 linking against shared libraries which don't have
7008 <tt>.la</tt> files, as it is a mere shell script it can
7009 add considerably to the build time of a
7010 <prgn>libtool</prgn>-using package if that shell script
7011 has to derive all this information from first principles
7012 for each library every time it is linked. With the
7013 advent of <prgn>libtool</prgn> version 1.4 (and to a
7014 lesser extent <prgn>libtool</prgn> version 1.3), the
7015 <file>.la</file> files also store information about
7016 inter-library dependencies which cannot necessarily be
7017 derived after the <file>.la</file> file is deleted.
7022 Packages that use <prgn>libtool</prgn> to create shared
7023 libraries should include the <file>.la</file> files in the
7024 <tt>-dev</tt> package, unless the package relies on
7025 <tt>libtool</tt>'s <tt>libltdl</tt> library, in which case
7026 the <tt>.la</tt> files must go in the run-time library
7031 You must make sure that you use only released versions of
7032 shared libraries to build your packages; otherwise other
7033 users will not be able to run your binaries
7034 properly. Producing source packages that depend on
7035 unreleased compilers is also usually a bad
7042 <heading>Shared libraries</heading>
7044 This section has moved to <ref id="sharedlibs">.
7050 <heading>Scripts</heading>
7053 All command scripts, including the package maintainer
7054 scripts inside the package and used by <prgn>dpkg</prgn>,
7055 should have a <tt>#!</tt> line naming the shell to be used
7060 In the case of Perl scripts this should be
7061 <tt>#!/usr/bin/perl</tt>.
7065 When scripts are installed into a directory in the system
7066 PATH, the script name should not include an extension such
7067 as <tt>.sh</tt> or <tt>.pl</tt> that denotes the scripting
7068 language currently used to implement it.
7071 Shell scripts (<prgn>sh</prgn> and <prgn>bash</prgn>)
7072 should almost certainly start with <tt>set -e</tt> so that
7073 errors are detected. Every script should use
7074 <tt>set -e</tt> or check the exit status of <em>every</em>
7079 Scripts may assume that <file>/bin/sh</file> implements the
7080 SUSv3 Shell Command Language<footnote>
7081 Single UNIX Specification, version 3, which is also IEEE
7082 1003.1-2004 (POSIX), and is available on the World Wide Web
7083 from <url id="http://www.unix.org/version3/online.html"
7084 name="The Open Group"> after free
7085 registration.</footnote>
7086 plus the following additional features not mandated by
7088 These features are in widespread use in the Linux community
7089 and are implemented in all of bash, dash, and ksh, the most
7090 common shells users may wish to use as <file>/bin/sh</file>.
7093 <item><tt>echo -n</tt>, if implemented as a shell built-in,
7094 must not generate a newline.</item>
7095 <item><tt>test</tt>, if implemented as a shell built-in, must
7096 support <tt>-a</tt> and <tt>-o</tt> as binary logical
7098 <item><tt>local</tt> to create a scoped variable must be
7099 supported, including listing multiple variables in a single
7100 local command and assigning a value to a variable at the
7101 same time as localizing it. <tt>local</tt> may or
7102 may not preserve the variable value from an outer scope if
7103 no assignment is present. Uses such as:
7107 # ... use a, b, c, d ...
7110 must be supported and must set the value of <tt>c</tt> to
7114 If a shell script requires non-SUSv3 features from the shell
7115 interpreter other than those listed above, the appropriate shell
7116 must be specified in the first line of the script (e.g.,
7117 <tt>#!/bin/bash</tt>) and the package must depend on the package
7118 providing the shell (unless the shell package is marked
7119 "Essential", as in the case of <prgn>bash</prgn>).
7123 You may wish to restrict your script to SUSv3 features plus the
7124 above set when possible so that it may use <file>/bin/sh</file>
7125 as its interpreter. If your script works with <prgn>dash</prgn>
7126 (originally called <prgn>ash</prgn>), it probably complies with
7127 the above requirements, but if you are in doubt, use
7128 <file>/bin/bash</file>.
7132 Perl scripts should check for errors when making any
7133 system calls, including <tt>open</tt>, <tt>print</tt>,
7134 <tt>close</tt>, <tt>rename</tt> and <tt>system</tt>.
7138 <prgn>csh</prgn> and <prgn>tcsh</prgn> should be avoided as
7139 scripting languages. See <em>Csh Programming Considered
7140 Harmful</em>, one of the <tt>comp.unix.*</tt> FAQs, which
7141 can be found at <url id="http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/">.
7142 If an upstream package comes with <prgn>csh</prgn> scripts
7143 then you must make sure that they start with
7144 <tt>#!/bin/csh</tt> and make your package depend on the
7145 <prgn>c-shell</prgn> virtual package.
7149 Any scripts which create files in world-writeable
7150 directories (e.g., in <file>/tmp</file>) must use a
7151 mechanism which will fail atomically if a file with the same
7152 name already exists.
7156 The Debian base system provides the <prgn>tempfile</prgn>
7157 and <prgn>mktemp</prgn> utilities for use by scripts for
7164 <heading>Symbolic links</heading>
7167 In general, symbolic links within a top-level directory
7168 should be relative, and symbolic links pointing from one
7169 top-level directory into another should be absolute. (A
7170 top-level directory is a sub-directory of the root
7171 directory <file>/</file>.)
7175 In addition, symbolic links should be specified as short as
7176 possible, i.e., link targets like <file>foo/../bar</file> are
7181 Note that when creating a relative link using
7182 <prgn>ln</prgn> it is not necessary for the target of the
7183 link to exist relative to the working directory you're
7184 running <prgn>ln</prgn> from, nor is it necessary to change
7185 directory to the directory where the link is to be made.
7186 Simply include the string that should appear as the target
7187 of the link (this will be a pathname relative to the
7188 directory in which the link resides) as the first argument
7193 For example, in your <prgn>Makefile</prgn> or
7194 <file>debian/rules</file>, you can do things like:
7195 <example compact="compact">
7196 ln -fs gcc $(prefix)/bin/cc
7197 ln -fs gcc debian/tmp/usr/bin/cc
7198 ln -fs ../sbin/sendmail $(prefix)/bin/runq
7199 ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
7204 A symbolic link pointing to a compressed file should always
7205 have the same file extension as the referenced file. (For
7206 example, if a file <file>foo.gz</file> is referenced by a
7207 symbolic link, the filename of the link has to end with
7208 "<file>.gz</file>" too, as in <file>bar.gz</file>.)
7213 <heading>Device files</heading>
7216 Packages must not include device files in the package file
7221 If a package needs any special device files that are not
7222 included in the base system, it must call
7223 <prgn>MAKEDEV</prgn> in the <prgn>postinst</prgn> script,
7224 after notifying the user<footnote>
7225 This notification could be done via a (low-priority)
7226 debconf message, or an echo (printf) statement.
7231 Packages must not remove any device files in the
7232 <prgn>postrm</prgn> or any other script. This is left to the
7233 system administrator.
7237 Debian uses the serial devices
7238 <file>/dev/ttyS*</file>. Programs using the old
7239 <file>/dev/cu*</file> devices should be changed to use
7240 <file>/dev/ttyS*</file>.
7244 <sect id="config-files">
7245 <heading>Configuration files</heading>
7248 <heading>Definitions</heading>
7252 <tag>configuration file</tag>
7254 A file that affects the operation of a program, or
7255 provides site- or host-specific information, or
7256 otherwise customizes the behavior of a program.
7257 Typically, configuration files are intended to be
7258 modified by the system administrator (if needed or
7259 desired) to conform to local policy or to provide
7260 more useful site-specific behavior.
7263 <tag><tt>conffile</tt></tag>
7265 A file listed in a package's <tt>conffiles</tt>
7266 file, and is treated specially by <prgn>dpkg</prgn>
7267 (see <ref id="configdetails">).
7273 The distinction between these two is important; they are
7274 not interchangeable concepts. Almost all
7275 <tt>conffile</tt>s are configuration files, but many
7276 configuration files are not <tt>conffiles</tt>.
7280 As noted elsewhere, <file>/etc/init.d</file> scripts,
7281 <file>/etc/default</file> files, scripts installed in
7282 <file>/etc/cron.{hourly,daily,weekly,monthly}</file>, and cron
7283 configuration installed in <file>/etc/cron.d</file> must be
7284 treated as configuration files. In general, any script that
7285 embeds configuration information is de-facto a configuration
7286 file and should be treated as such.
7291 <heading>Location</heading>
7294 Any configuration files created or used by your package
7295 must reside in <file>/etc</file>. If there are several,
7296 consider creating a subdirectory of <file>/etc</file>
7297 named after your package.
7301 If your package creates or uses configuration files
7302 outside of <file>/etc</file>, and it is not feasible to modify
7303 the package to use <file>/etc</file> directly, put the files
7304 in <file>/etc</file> and create symbolic links to those files
7305 from the location that the package requires.
7310 <heading>Behavior</heading>
7313 Configuration file handling must conform to the following
7315 <list compact="compact">
7317 local changes must be preserved during a package
7321 configuration files must be preserved when the
7322 package is removed, and only deleted when the
7329 The easy way to achieve this behavior is to make the
7330 configuration file a <tt>conffile</tt>. This is
7331 appropriate only if it is possible to distribute a default
7332 version that will work for most installations, although
7333 some system administrators may choose to modify it. This
7334 implies that the default version will be part of the
7335 package distribution, and must not be modified by the
7336 maintainer scripts during installation (or at any other
7341 In order to ensure that local changes are preserved
7342 correctly, no package may contain or make hard links to
7343 conffiles.<footnote>
7344 Rationale: There are two problems with hard links.
7345 The first is that some editors break the link while
7346 editing one of the files, so that the two files may
7347 unwittingly become unlinked and different. The second
7348 is that <prgn>dpkg</prgn> might break the hard link
7349 while upgrading <tt>conffile</tt>s.
7354 The other way to do it is via the maintainer scripts. In
7355 this case, the configuration file must not be listed as a
7356 <tt>conffile</tt> and must not be part of the package
7357 distribution. If the existence of a file is required for
7358 the package to be sensibly configured it is the
7359 responsibility of the package maintainer to provide
7360 maintainer scripts which correctly create, update and
7361 maintain the file and remove it on purge. (See <ref
7362 id="maintainerscripts"> for more information.) These
7363 scripts must be idempotent (i.e., must work correctly if
7364 <prgn>dpkg</prgn> needs to re-run them due to errors
7365 during installation or removal), must cope with all the
7366 variety of ways <prgn>dpkg</prgn> can call maintainer
7367 scripts, must not overwrite or otherwise mangle the user's
7368 configuration without asking, must not ask unnecessary
7369 questions (particularly during upgrades), and must
7370 otherwise be good citizens.
7374 The scripts are not required to configure every possible
7375 option for the package, but only those necessary to get
7376 the package running on a given system. Ideally the
7377 sysadmin should not have to do any configuration other
7378 than that done (semi-)automatically by the
7379 <prgn>postinst</prgn> script.
7383 A common practice is to create a script called
7384 <file><var>package</var>-configure</file> and have the
7385 package's <prgn>postinst</prgn> call it if and only if the
7386 configuration file does not already exist. In certain
7387 cases it is useful for there to be an example or template
7388 file which the maintainer scripts use. Such files should
7389 be in <file>/usr/share/<var>package</var></file> or
7390 <file>/usr/lib/<var>package</var></file> (depending on whether
7391 they are architecture-independent or not). There should
7392 be symbolic links to them from
7393 <file>/usr/share/doc/<var>package</var>/examples</file> if
7394 they are examples, and should be perfectly ordinary
7395 <prgn>dpkg</prgn>-handled files (<em>not</em>
7396 configuration files).
7400 These two styles of configuration file handling must
7401 not be mixed, for that way lies madness:
7402 <prgn>dpkg</prgn> will ask about overwriting the file
7403 every time the package is upgraded.
7408 <heading>Sharing configuration files</heading>
7411 Packages which specify the same file as a
7412 <tt>conffile</tt> must be tagged as <em>conflicting</em>
7413 with each other. (This is an instance of the general rule
7414 about not sharing files. Note that neither alternatives
7415 nor diversions are likely to be appropriate in this case;
7416 in particular, <prgn>dpkg</prgn> does not handle diverted
7417 <tt>conffile</tt>s well.)
7421 The maintainer scripts must not alter a <tt>conffile</tt>
7422 of <em>any</em> package, including the one the scripts
7427 If two or more packages use the same configuration file
7428 and it is reasonable for both to be installed at the same
7429 time, one of these packages must be defined as
7430 <em>owner</em> of the configuration file, i.e., it will be
7431 the package which handles that file as a configuration
7432 file. Other packages that use the configuration file must
7433 depend on the owning package if they require the
7434 configuration file to operate. If the other package will
7435 use the configuration file if present, but is capable of
7436 operating without it, no dependency need be declared.
7440 If it is desirable for two or more related packages to
7441 share a configuration file <em>and</em> for all of the
7442 related packages to be able to modify that configuration
7443 file, then the following should be done:
7444 <enumlist compact="compact">
7446 One of the related packages (the "owning" package)
7447 will manage the configuration file with maintainer
7448 scripts as described in the previous section.
7451 The owning package should also provide a program
7452 that the other packages may use to modify the
7456 The related packages must use the provided program
7457 to make any desired modifications to the
7458 configuration file. They should either depend on
7459 the core package to guarantee that the configuration
7460 modifier program is available or accept gracefully
7461 that they cannot modify the configuration file if it
7462 is not. (This is in addition to the fact that the
7463 configuration file may not even be present in the
7470 Sometimes it's appropriate to create a new package which
7471 provides the basic infrastructure for the other packages
7472 and which manages the shared configuration files. (The
7473 <tt>sgml-base</tt> package is a good example.)
7478 <heading>User configuration files ("dotfiles")</heading>
7481 The files in <file>/etc/skel</file> will automatically be
7482 copied into new user accounts by <prgn>adduser</prgn>.
7483 No other program should reference the files in
7484 <file>/etc/skel</file>.
7488 Therefore, if a program needs a dotfile to exist in
7489 advance in <file>$HOME</file> to work sensibly, that dotfile
7490 should be installed in <file>/etc/skel</file> and treated as a
7495 However, programs that require dotfiles in order to
7496 operate sensibly are a bad thing, unless they do create
7497 the dotfiles themselves automatically.
7501 Furthermore, programs should be configured by the Debian
7502 default installation to behave as closely to the upstream
7503 default behavior as possible.
7507 Therefore, if a program in a Debian package needs to be
7508 configured in some way in order to operate sensibly, that
7509 should be done using a site-wide configuration file placed
7510 in <file>/etc</file>. Only if the program doesn't support a
7511 site-wide default configuration and the package maintainer
7512 doesn't have time to add it may a default per-user file be
7513 placed in <file>/etc/skel</file>.
7517 <file>/etc/skel</file> should be as empty as we can make it.
7518 This is particularly true because there is no easy (or
7519 necessarily desirable) mechanism for ensuring that the
7520 appropriate dotfiles are copied into the accounts of
7521 existing users when a package is installed.
7527 <heading>Log files</heading>
7529 Log files should usually be named
7530 <file>/var/log/<var>package</var>.log</file>. If you have many
7531 log files, or need a separate directory for permission
7532 reasons (<file>/var/log</file> is writable only by
7533 <file>root</file>), you should usually create a directory named
7534 <file>/var/log/<var>package</var></file> and place your log
7539 Log files must be rotated occasionally so that they don't
7540 grow indefinitely; the best way to do this is to drop a log
7541 rotation configuration file into the directory
7542 <file>/etc/logrotate.d</file> and use the facilities provided by
7543 logrotate.<footnote>
7545 The traditional approach to log files has been to set up
7546 <em>ad hoc</em> log rotation schemes using simple shell
7547 scripts and cron. While this approach is highly
7548 customizable, it requires quite a lot of sysadmin work.
7549 Even though the original Debian system helped a little
7550 by automatically installing a system which can be used
7551 as a template, this was deemed not enough.
7555 The use of <prgn>logrotate</prgn>, a program developed
7556 by Red Hat, is better, as it centralizes log management.
7557 It has both a configuration file
7558 (<file>/etc/logrotate.conf</file>) and a directory where
7559 packages can drop their individual log rotation
7560 configurations (<file>/etc/logrotate.d</file>).
7563 Here is a good example for a logrotate config
7564 file (for more information see <manref name="logrotate"
7566 <example compact="compact">
7567 /var/log/foo/*.log {
7572 /etc/init.d/foo force-reload
7576 This rotates all files under <file>/var/log/foo</file>, saves 12
7577 compressed generations, and forces the daemon to reload its
7578 configuration information after the log rotation.
7582 Log files should be removed when the package is
7583 purged (but not when it is only removed). This should be
7584 done by the <prgn>postrm</prgn> script when it is called
7585 with the argument <tt>purge</tt> (see <ref
7586 id="removedetails">).
7591 <heading>Permissions and owners</heading>
7594 The rules in this section are guidelines for general use.
7595 If necessary you may deviate from the details below.
7596 However, if you do so you must make sure that what is done
7597 is secure and you should try to be as consistent as possible
7598 with the rest of the system. You should probably also
7599 discuss it on <prgn>debian-devel</prgn> first.
7603 Files should be owned by <tt>root:root</tt>, and made
7604 writable only by the owner and universally readable (and
7605 executable, if appropriate), that is mode 644 or 755.
7609 Directories should be mode 755 or (for group-writability)
7610 mode 2775. The ownership of the directory should be
7611 consistent with its mode: if a directory is mode 2775, it
7612 should be owned by the group that needs write access to
7615 When a package is upgraded, and the owner or permissions
7616 of a file included in the package has changed, dpkg
7617 arranges for the ownership and permissions to be
7618 correctly set upon installation. However, this does not
7619 extend to directories; the permissions and ownership of
7620 directories already on the system does not change on
7621 install or upgrade of packages. This makes sense, since
7622 otherwise common directories like <tt>/usr</tt> would
7623 always be in flux. To correctly change permissions of a
7624 directory the package owns, explicit action is required,
7625 usually in the <tt>postinst</tt> script. Care must be
7626 taken to handle downgrades as well, in that case.
7633 Setuid and setgid executables should be mode 4755 or 2755
7634 respectively, and owned by the appropriate user or group.
7635 They should not be made unreadable (modes like 4711 or
7636 2711 or even 4111); doing so achieves no extra security,
7637 because anyone can find the binary in the freely available
7638 Debian package; it is merely inconvenient. For the same
7639 reason you should not restrict read or execute permissions
7640 on non-set-id executables.
7644 Some setuid programs need to be restricted to particular
7645 sets of users, using file permissions. In this case they
7646 should be owned by the uid to which they are set-id, and by
7647 the group which should be allowed to execute them. They
7648 should have mode 4754; again there is no point in making
7649 them unreadable to those users who must not be allowed to
7654 It is possible to arrange that the system administrator can
7655 reconfigure the package to correspond to their local
7656 security policy by changing the permissions on a binary:
7657 they can do this by using <prgn>dpkg-statoverride</prgn>, as
7658 described below.<footnote>
7659 Ordinary files installed by <prgn>dpkg</prgn> (as
7660 opposed to <tt>conffile</tt>s and other similar objects)
7661 normally have their permissions reset to the distributed
7662 permissions when the package is reinstalled. However,
7663 the use of <prgn>dpkg-statoverride</prgn> overrides this
7664 default behavior. If you use this method, you should
7665 remember to describe <prgn>dpkg-statoverride</prgn> in
7666 the package documentation; being a relatively new
7667 addition to Debian, it is probably not yet well-known.
7669 Another method you should consider is to create a group for
7670 people allowed to use the program(s) and make any setuid
7671 executables executable only by that group.
7675 If you need to create a new user or group for your package
7676 there are two possibilities. Firstly, you may need to
7677 make some files in the binary package be owned by this
7678 user or group, or you may need to compile the user or
7679 group id (rather than just the name) into the binary
7680 (though this latter should be avoided if possible, as in
7681 this case you need a statically allocated id).</p>
7684 If you need a statically allocated id, you must ask for a
7685 user or group id from the <tt>base-passwd</tt> maintainer,
7686 and must not release the package until you have been
7687 allocated one. Once you have been allocated one you must
7688 either make the package depend on a version of the
7689 <tt>base-passwd</tt> package with the id present in
7690 <file>/etc/passwd</file> or <file>/etc/group</file>, or arrange for
7691 your package to create the user or group itself with the
7692 correct id (using <tt>adduser</tt>) in its
7693 <prgn>preinst</prgn> or <prgn>postinst</prgn>. (Doing it in
7694 the <prgn>postinst</prgn> is to be preferred if it is
7695 possible, otherwise a pre-dependency will be needed on the
7696 <tt>adduser</tt> package.)
7700 On the other hand, the program might be able to determine
7701 the uid or gid from the user or group name at runtime, so
7702 that a dynamically allocated id can be used. In this case
7703 you should choose an appropriate user or group name,
7704 discussing this on <prgn>debian-devel</prgn> and checking
7705 with the <package/base-passwd/ maintainer that it is unique and that
7706 they do not wish you to use a statically allocated id
7707 instead. When this has been checked you must arrange for
7708 your package to create the user or group if necessary using
7709 <prgn>adduser</prgn> in the <prgn>preinst</prgn> or
7710 <prgn>postinst</prgn> script (again, the latter is to be
7711 preferred if it is possible).
7715 Note that changing the numeric value of an id associated
7716 with a name is very difficult, and involves searching the
7717 file system for all appropriate files. You need to think
7718 carefully whether a static or dynamic id is required, since
7719 changing your mind later will cause problems.
7722 <sect1><heading>The use of <prgn>dpkg-statoverride</prgn></heading>
7724 This section is not intended as policy, but as a
7725 description of the use of <prgn>dpkg-statoverride</prgn>.
7729 If a system administrator wishes to have a file (or
7730 directory or other such thing) installed with owner and
7731 permissions different from those in the distributed Debian
7732 package, they can use the <prgn>dpkg-statoverride</prgn>
7733 program to instruct <prgn>dpkg</prgn> to use the different
7734 settings every time the file is installed. Thus the
7735 package maintainer should distribute the files with their
7736 normal permissions, and leave it for the system
7737 administrator to make any desired changes. For example, a
7738 daemon which is normally required to be setuid root, but
7739 in certain situations could be used without being setuid,
7740 should be installed setuid in the <tt>.deb</tt>. Then the
7741 local system administrator can change this if they wish.
7742 If there are two standard ways of doing it, the package
7743 maintainer can use <tt>debconf</tt> to find out the
7744 preference, and call <prgn>dpkg-statoverride</prgn> in the
7745 maintainer script if necessary to accommodate the system
7746 administrator's choice. Care must be taken during
7747 upgrades to not override an existing setting.
7751 Given the above, <prgn>dpkg-statoverride</prgn> is
7752 essentially a tool for system administrators and would not
7753 normally be needed in the maintainer scripts. There is
7754 one type of situation, though, where calls to
7755 <prgn>dpkg-statoverride</prgn> would be needed in the
7756 maintainer scripts, and that involves packages which use
7757 dynamically allocated user or group ids. In such a
7758 situation, something like the following idiom can be very
7759 helpful in the package's <prgn>postinst</prgn>, where
7760 <tt>sysuser</tt> is a dynamically allocated id:
7762 for i in /usr/bin/foo /usr/sbin/bar
7764 # only do something when no setting exists
7765 if ! dpkg-statoverride --list $i >/dev/null 2>&1
7767 #include: debconf processing, question about foo and bar
7768 if [ "$RET" = "true" ] ; then
7769 dpkg-statoverride --update --add sysuser root 4755 $i
7774 The corresponding <tt>dpkg-statoverride --remove</tt>
7775 calls can then be made unconditionally when the package is
7783 <chapt id="customized-programs">
7784 <heading>Customized programs</heading>
7786 <sect id="arch-spec">
7787 <heading>Architecture specification strings</heading>
7790 If a program needs to specify an <em>architecture specification
7791 string</em> in some place, it should select one of the
7792 strings provided by <tt>dpkg-architecture -L</tt>. The
7793 strings are in the format
7794 <tt><var>os</var>-<var>arch</var></tt>, though the OS part
7795 is sometimes elided, as when the OS is Linux.<footnote>
7796 <p>Currently, the strings are:
7797 i386 ia64 alpha amd64 armeb arm hppa m32r m68k mips
7798 mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb
7799 sparc darwin-i386 darwin-ia64 darwin-alpha darwin-amd64
7800 darwin-armeb darwin-arm darwin-hppa darwin-m32r
7801 darwin-m68k darwin-mips darwin-mipsel darwin-powerpc
7802 darwin-ppc64 darwin-s390 darwin-s390x darwin-sh3
7803 darwin-sh3eb darwin-sh4 darwin-sh4eb darwin-sparc
7804 freebsd-i386 freebsd-ia64 freebsd-alpha freebsd-amd64
7805 freebsd-armeb freebsd-arm freebsd-hppa freebsd-m32r
7806 freebsd-m68k freebsd-mips freebsd-mipsel freebsd-powerpc
7807 freebsd-ppc64 freebsd-s390 freebsd-s390x freebsd-sh3
7808 freebsd-sh3eb freebsd-sh4 freebsd-sh4eb freebsd-sparc
7809 kfreebsd-i386 kfreebsd-ia64 kfreebsd-alpha
7810 kfreebsd-amd64 kfreebsd-armeb kfreebsd-arm kfreebsd-hppa
7811 kfreebsd-m32r kfreebsd-m68k kfreebsd-mips
7812 kfreebsd-mipsel kfreebsd-powerpc kfreebsd-ppc64
7813 kfreebsd-s390 kfreebsd-s390x kfreebsd-sh3 kfreebsd-sh3eb
7814 kfreebsd-sh4 kfreebsd-sh4eb kfreebsd-sparc knetbsd-i386
7815 knetbsd-ia64 knetbsd-alpha knetbsd-amd64 knetbsd-armeb
7816 knetbsd-arm knetbsd-hppa knetbsd-m32r knetbsd-m68k
7817 knetbsd-mips knetbsd-mipsel knetbsd-powerpc
7818 knetbsd-ppc64 knetbsd-s390 knetbsd-s390x knetbsd-sh3
7819 knetbsd-sh3eb knetbsd-sh4 knetbsd-sh4eb knetbsd-sparc
7820 netbsd-i386 netbsd-ia64 netbsd-alpha netbsd-amd64
7821 netbsd-armeb netbsd-arm netbsd-hppa netbsd-m32r
7822 netbsd-m68k netbsd-mips netbsd-mipsel netbsd-powerpc
7823 netbsd-ppc64 netbsd-s390 netbsd-s390x netbsd-sh3
7824 netbsd-sh3eb netbsd-sh4 netbsd-sh4eb netbsd-sparc
7825 openbsd-i386 openbsd-ia64 openbsd-alpha openbsd-amd64
7826 openbsd-armeb openbsd-arm openbsd-hppa openbsd-m32r
7827 openbsd-m68k openbsd-mips openbsd-mipsel openbsd-powerpc
7828 openbsd-ppc64 openbsd-s390 openbsd-s390x openbsd-sh3
7829 openbsd-sh3eb openbsd-sh4 openbsd-sh4eb openbsd-sparc
7830 hurd-i386 hurd-ia64 hurd-alpha hurd-amd64 hurd-armeb
7831 hurd-arm hurd-hppa hurd-m32r hurd-m68k hurd-mips
7832 hurd-mipsel hurd-powerpc hurd-ppc64 hurd-s390 hurd-s390x
7833 hurd-sh3 hurd-sh3eb hurd-sh4 hurd-sh4eb hurd-sparc
7839 Note that we don't want to use
7840 <tt><var>arch</var>-debian-linux</tt> to apply to the rule
7841 <tt><var>architecture</var>-<var>vendor</var>-<var>os</var></tt>
7842 since this would make our programs incompatible with other
7843 Linux distributions. We also don't use something like
7844 <tt><var>arch</var>-unknown-linux</tt>, since the
7845 <tt>unknown</tt> does not look very good.
7850 <heading>Daemons</heading>
7853 The configuration files <file>/etc/services</file>,
7854 <file>/etc/protocols</file>, and <file>/etc/rpc</file> are managed
7855 by the <prgn>netbase</prgn> package and must not be modified
7860 If a package requires a new entry in one of these files, the
7861 maintainer should get in contact with the
7862 <prgn>netbase</prgn> maintainer, who will add the entries
7863 and release a new version of the <prgn>netbase</prgn>
7868 The configuration file <file>/etc/inetd.conf</file> must not be
7869 modified by the package's scripts except via the
7870 <prgn>update-inetd</prgn> script or the
7871 <file>DebianNet.pm</file> Perl module. See their documentation
7872 for details on how to add entries.
7876 If a package wants to install an example entry into
7877 <file>/etc/inetd.conf</file>, the entry must be preceded with
7878 exactly one hash character (<tt>#</tt>). Such lines are
7879 treated as "commented out by user" by the
7880 <prgn>update-inetd</prgn> script and are not changed or
7881 activated during package updates.
7886 <heading>Using pseudo-ttys and modifying wtmp, utmp and
7890 Some programs need to create pseudo-ttys. This should be done
7891 using Unix98 ptys if the C library supports it. The resulting
7892 program must not be installed setuid root, unless that
7893 is required for other functionality.
7897 The files <file>/var/run/utmp</file>, <file>/var/log/wtmp</file> and
7898 <file>/var/log/lastlog</file> must be installed writable by
7899 group <tt>utmp</tt>. Programs which need to modify those
7900 files must be installed setgid <tt>utmp</tt>.
7905 <heading>Editors and pagers</heading>
7908 Some programs have the ability to launch an editor or pager
7909 program to edit or display a text document. Since there are
7910 lots of different editors and pagers available in the Debian
7911 distribution, the system administrator and each user should
7912 have the possibility to choose their preferred editor and
7917 In addition, every program should choose a good default
7918 editor/pager if none is selected by the user or system
7923 Thus, every program that launches an editor or pager must
7924 use the EDITOR or PAGER environment variable to determine
7925 the editor or pager the user wishes to use. If these
7926 variables are not set, the programs <file>/usr/bin/editor</file>
7927 and <file>/usr/bin/pager</file> should be used, respectively.
7931 These two files are managed through the <prgn>dpkg</prgn>
7932 "alternatives" mechanism. Thus every package providing an
7933 editor or pager must call the
7934 <prgn>update-alternatives</prgn> script to register these
7939 If it is very hard to adapt a program to make use of the
7940 EDITOR or PAGER variables, that program may be configured to
7941 use <file>/usr/bin/sensible-editor</file> and
7942 <file>/usr/bin/sensible-pager</file> as the editor or pager
7943 program respectively. These are two scripts provided in the
7944 Debian base system that check the EDITOR and PAGER variables
7945 and launch the appropriate program, and fall back to
7946 <file>/usr/bin/editor</file> and <file>/usr/bin/pager</file> if the
7947 variable is not set.
7951 A program may also use the VISUAL environment variable to
7952 determine the user's choice of editor. If it exists, it
7953 should take precedence over EDITOR. This is in fact what
7954 <file>/usr/bin/sensible-editor</file> does.
7958 It is not required for a package to depend on
7959 <tt>editor</tt> and <tt>pager</tt>, nor is it required for a
7960 package to provide such virtual packages.<footnote>
7961 The Debian base system already provides an editor and a
7967 <sect id="web-appl">
7968 <heading>Web servers and applications</heading>
7971 This section describes the locations and URLs that should
7972 be used by all web servers and web applications in the
7979 Cgi-bin executable files are installed in the
7981 <example compact="compact">
7982 /usr/lib/cgi-bin/<var>cgi-bin-name</var>
7984 and should be referred to as
7985 <example compact="compact">
7986 http://localhost/cgi-bin/<var>cgi-bin-name</var>
7992 <p>Access to HTML documents</p>
7995 HTML documents for a package are stored in
7996 <file>/usr/share/doc/<var>package</var></file>
7997 and can be referred to as
7998 <example compact="compact">
7999 http://localhost/doc/<var>package</var>/<var>filename</var>
8004 The web server should restrict access to the document
8005 tree so that only clients on the same host can read
8006 the documents. If the web server does not support such
8007 access controls, then it should not provide access at
8008 all, or ask about providing access during installation.
8013 <p>Access to images</p>
8015 It is recommended that images for a package be stored
8016 in <tt>/usr/share/images/<var>package</var></tt> and
8017 may be referred to through an alias <tt>/images/</tt>
8020 http://localhost/images/<package>/<filename>
8027 <p>Web Document Root</p>
8030 Web Applications should try to avoid storing files in
8031 the Web Document Root. Instead they should use the
8032 /usr/share/doc/<var>package</var> directory for
8033 documents and register the Web Application via the
8034 <package>doc-base</package> package. If access to the
8035 web document root is unavoidable then use
8036 <example compact="compact">
8039 as the Document Root. This might be just a symbolic
8040 link to the location where the system administrator
8041 has put the real document root.
8044 <item><p>Providing httpd and/or httpd-cgi</p>
8046 All web servers should provide the virtual package
8047 <tt>httpd</tt>. If a web server has CGI support it should
8048 provide <tt>httpd-cgi</tt> additionally.
8051 All web applications which do not contain CGI scripts should
8052 depend on <tt>httpd</tt>, all those web applications which
8053 <tt>do</tt> contain CGI scripts, should depend on
8061 <sect id="mail-transport-agents">
8062 <heading>Mail transport, delivery and user agents</heading>
8065 Debian packages which process electronic mail, whether mail
8066 user agents (MUAs) or mail transport agents (MTAs), must
8067 ensure that they are compatible with the configuration
8068 decisions below. Failure to do this may result in lost
8069 mail, broken <tt>From:</tt> lines, and other serious brain
8074 The mail spool is <file>/var/mail</file> and the interface to
8075 send a mail message is <file>/usr/sbin/sendmail</file> (as per
8076 the FHS). On older systems, the mail spool may be
8077 physically located in <file>/var/spool/mail</file>, but all
8078 access to the mail spool should be via the
8079 <file>/var/mail</file> symlink. The mail spool is part of the
8080 base system and not part of the MTA package.
8084 All Debian MUAs, MTAs, MDAs and other mailbox accessing
8085 programs (such as IMAP daemons) must lock the mailbox in an
8086 NFS-safe way. This means that <tt>fcntl()</tt> locking must
8087 be combined with dot locking. To avoid deadlocks, a program
8088 should use <tt>fcntl()</tt> first and dot locking after
8089 this, or alternatively implement the two locking methods in
8090 a non blocking way<footnote>
8091 If it is not possible to establish both locks, the
8092 system shouldn't wait for the second lock to be
8093 established, but remove the first lock, wait a (random)
8094 time, and start over locking again.
8095 </footnote>. Using the functions <tt>maillock</tt> and
8096 <tt>mailunlock</tt> provided by the
8097 <tt>liblockfile*</tt><footnote>
8098 You will need to depend on <tt>liblockfile1 (>>1.01)</tt>
8099 to use these functions.
8100 </footnote> packages is the recommended way to realize this.
8104 Mailboxes are generally either mode 600 and owned by
8105 <var>user</var> or mode 660 and owned by
8106 <tt><var>user</var>:mail</tt><footnote>
8107 There are two traditional permission schemes for mail spools:
8108 mode 600 with all mail delivery done by processes running as
8109 the destination user, or mode 660 and owned by group mail with
8110 mail delivery done by a process running as a system user in
8111 group mail. Historically, Debian required mode 660 mail
8112 spools to enable the latter model, but that model has become
8113 increasingly uncommon and the principle of least privilege
8114 indicates that mail systems that use the first model should
8115 use permissions of 600. If delivery to programs is permitted,
8116 it's easier to keep the mail system secure if the delivery
8117 agent runs as the destination user. Debian Policy therefore
8118 permits either scheme.
8119 </footnote>. The local system administrator may choose a
8120 different permission scheme; packages should not make
8121 assumptions about the permission and ownership of mailboxes
8122 unless required (such as when creating a new mailbox). A MUA
8123 may remove a mailbox (unless it has nonstandard permissions) in
8124 which case the MTA or another MUA must recreate it if needed.
8128 The mail spool is 2775 <tt>root:mail</tt>, and MUAs should
8129 be setgid mail to do the locking mentioned above (and
8130 must obviously avoid accessing other users' mailboxes
8131 using this privilege).</p>
8134 <file>/etc/aliases</file> is the source file for the system mail
8135 aliases (e.g., postmaster, usenet, etc.), it is the one
8136 which the sysadmin and <prgn>postinst</prgn> scripts may
8137 edit. After <file>/etc/aliases</file> is edited the program or
8138 human editing it must call <prgn>newaliases</prgn>. All MTA
8139 packages must come with a <prgn>newaliases</prgn> program,
8140 even if it does nothing, but older MTA packages did not do
8141 this so programs should not fail if <prgn>newaliases</prgn>
8142 cannot be found. Note that because of this, all MTA
8143 packages must have <tt>Provides</tt>, <tt>Conflicts</tt> and
8144 <tt>Replaces: mail-transport-agent</tt> control file
8149 The convention of writing <tt>forward to
8150 <var>address</var></tt> in the mailbox itself is not
8151 supported. Use a <tt>.forward</tt> file instead.</p>
8154 The <prgn>rmail</prgn> program used by UUCP
8155 for incoming mail should be <file>/usr/sbin/rmail</file>.
8156 Likewise, <prgn>rsmtp</prgn>, for receiving
8157 batch-SMTP-over-UUCP, should be <file>/usr/sbin/rsmtp</file> if it
8161 If your package needs to know what hostname to use on (for
8162 example) outgoing news and mail messages which are generated
8163 locally, you should use the file <file>/etc/mailname</file>. It
8164 will contain the portion after the username and <tt>@</tt>
8165 (at) sign for email addresses of users on the machine
8166 (followed by a newline).
8170 Such a package should check for the existence of this file
8171 when it is being configured. If it exists, it should be
8172 used without comment, although an MTA's configuration script
8173 may wish to prompt the user even if it finds that this file
8174 exists. If the file does not exist, the package should
8175 prompt the user for the value (preferably using
8176 <prgn>debconf</prgn>) and store it in <file>/etc/mailname</file>
8177 as well as using it in the package's configuration. The
8178 prompt should make it clear that the name will not just be
8179 used by that package. For example, in this situation the
8180 <tt>inn</tt> package could say something like:
8181 <example compact="compact">
8182 Please enter the "mail name" of your system. This is the
8183 hostname portion of the address to be shown on outgoing
8184 news and mail messages. The default is
8185 <var>syshostname</var>, your system's host name. Mail
8186 name ["<var>syshostname</var>"]:
8188 where <var>syshostname</var> is the output of <tt>hostname
8194 <heading>News system configuration</heading>
8197 All the configuration files related to the NNTP (news)
8198 servers and clients should be located under
8199 <file>/etc/news</file>.</p>
8202 There are some configuration issues that apply to a number
8203 of news clients and server packages on the machine. These
8207 <tag><file>/etc/news/organization</file></tag>
8209 A string which should appear as the
8210 organization header for all messages posted
8211 by NNTP clients on the machine
8214 <tag><file>/etc/news/server</file></tag>
8216 Contains the FQDN of the upstream NNTP
8217 server, or localhost if the local machine is
8222 Other global files may be added as required for cross-package news
8229 <heading>Programs for the X Window System</heading>
8232 <heading>Providing X support and package priorities</heading>
8235 Programs that can be configured with support for the X
8236 Window System must be configured to do so and must declare
8237 any package dependencies necessary to satisfy their
8238 runtime requirements when using the X Window System. If
8239 such a package is of higher priority than the X packages
8240 on which it depends, it is required that either the
8241 X-specific components be split into a separate package, or
8242 that an alternative version of the package, which includes
8243 X support, be provided, or that the package's priority be
8249 <heading>Packages providing an X server</heading>
8252 Packages that provide an X server that, directly or
8253 indirectly, communicates with real input and display
8254 hardware should declare in their control data that they
8255 provide the virtual package <tt>xserver</tt>.<footnote>
8256 This implements current practice, and provides an
8257 actual policy for usage of the <tt>xserver</tt>
8258 virtual package which appears in the virtual packages
8259 list. In a nutshell, X servers that interface
8260 directly with the display and input hardware or via
8261 another subsystem (e.g., GGI) should provide
8262 <tt>xserver</tt>. Things like <tt>Xvfb</tt>,
8263 <tt>Xnest</tt>, and <tt>Xprt</tt> should not.
8269 <heading>Packages providing a terminal emulator</heading>
8272 Packages that provide a terminal emulator for the X Window
8273 System which meet the criteria listed below should declare
8274 in their control data that they provide the virtual
8275 package <tt>x-terminal-emulator</tt>. They should also
8276 register themselves as an alternative for
8277 <file>/usr/bin/x-terminal-emulator</file>, with a priority of
8282 To be an <tt>x-terminal-emulator</tt>, a program must:
8283 <list compact="compact">
8285 Be able to emulate a DEC VT100 terminal, or a
8286 compatible terminal.
8290 Support the command-line option <tt>-e
8291 <var>command</var></tt>, which creates a new
8292 terminal window<footnote>
8293 "New terminal window" does not necessarily mean
8294 a new top-level X window directly parented by
8295 the window manager; it could, if the terminal
8296 emulator application were so coded, be a new
8297 "view" in a multiple-document interface (MDI).
8299 and runs the specified <var>command</var>,
8300 interpreting the entirety of the rest of the command
8301 line as a command to pass straight to exec, in the
8302 manner that <tt>xterm</tt> does.
8306 Support the command-line option <tt>-T
8307 <var>title</var></tt>, which creates a new terminal
8308 window with the window title <var>title</var>.
8315 <heading>Packages providing a window manager</heading>
8318 Packages that provide a window manager should declare in
8319 their control data that they provide the virtual package
8320 <tt>x-window-manager</tt>. They should also register
8321 themselves as an alternative for
8322 <file>/usr/bin/x-window-manager</file>, with a priority
8323 calculated as follows:
8324 <list compact="compact">
8326 Start with a priority of 20.
8330 If the window manager supports the Debian menu
8331 system, add 20 points if this support is available
8332 in the package's default configuration (i.e., no
8333 configuration files belonging to the system or user
8334 have to be edited to activate the feature); if
8335 configuration files must be modified, add only 10
8341 If the window manager complies with <url
8342 id="http://www.freedesktop.org/Standards/wm-spec"
8343 name="The Window Manager Specification Project">,
8344 written by the <url id="http://www.freedesktop.org/"
8345 name="Free Desktop Group">, add 40 points.
8349 If the window manager permits the X session to be
8350 restarted using a <em>different</em> window manager
8351 (without killing the X server) in its default
8352 configuration, add 10 points; otherwise add none.
8359 <heading>Packages providing fonts</heading>
8362 Packages that provide fonts for the X Window
8364 For the purposes of Debian Policy, a "font for the X
8365 Window System" is one which is accessed via X protocol
8366 requests. Fonts for the Linux console, for PostScript
8367 renderer, or any other purpose, do not fit this
8368 definition. Any tool which makes such fonts available
8369 to the X Window System, however, must abide by this
8372 must do a number of things to ensure that they are both
8373 available without modification of the X or font server
8374 configuration, and that they do not corrupt files used by
8375 other font packages to register information about
8379 Fonts of any type supported by the X Window System
8380 must be in a separate binary package from any
8381 executables, libraries, or documentation (except
8382 that specific to the fonts shipped, such as their
8383 license information). If one or more of the fonts
8384 so packaged are necessary for proper operation of
8385 the package with which they are associated the font
8386 package may be Recommended; if the fonts merely
8387 provide an enhancement, a Suggests relationship may
8388 be used. Packages must not Depend on font
8390 This is because the X server may retrieve fonts
8391 from the local file system or over the network
8392 from an X font server; the Debian package system
8393 is empowered to deal only with the local
8399 BDF fonts must be converted to PCF fonts with the
8400 <prgn>bdftopcf</prgn> utility (available in the
8401 <tt>xfonts-utils</tt> package, <prgn>gzip</prgn>ped, and
8402 placed in a directory that corresponds to their
8404 <list compact="compact">
8406 100 dpi fonts must be placed in
8407 <file>/usr/share/fonts/X11/100dpi/</file>.
8411 75 dpi fonts must be placed in
8412 <file>/usr/share/fonts/X11/75dpi/</file>.
8416 Character-cell fonts, cursor fonts, and other
8417 low-resolution fonts must be placed in
8418 <file>/usr/share/fonts/X11/misc/</file>.
8424 Type 1 fonts must be placed in
8425 <file>/usr/share/fonts/X11/Type1/</file>. If font
8426 metric files are available, they must be placed here
8431 Subdirectories of <file>/usr/share/fonts/X11/</file>
8432 other than those listed above must be neither
8433 created nor used. (The <file>PEX</file>, <file>CID</file>,
8434 <file>Speedo</file>, and <file>cyrillic</file> directories
8435 are excepted for historical reasons, but installation of
8436 files into these directories remains discouraged.)
8440 Font packages may, instead of placing files directly
8441 in the X font directories listed above, provide
8442 symbolic links in that font directory pointing to
8443 the files' actual location in the filesystem. Such
8444 a location must comply with the FHS.
8448 Font packages should not contain both 75dpi and
8449 100dpi versions of a font. If both are available,
8450 they should be provided in separate binary packages
8451 with <tt>-75dpi</tt> or <tt>-100dpi</tt> appended to
8452 the names of the packages containing the
8453 corresponding fonts.
8457 Fonts destined for the <file>misc</file> subdirectory
8458 should not be included in the same package as 75dpi
8459 or 100dpi fonts; instead, they should be provided in
8460 a separate package with <tt>-misc</tt> appended to
8465 Font packages must not provide the files
8466 <file>fonts.dir</file>, <file>fonts.alias</file>, or
8467 <file>fonts.scale</file> in a font directory:
8470 <file>fonts.dir</file> files must not be provided at all.
8474 <file>fonts.alias</file> and <file>fonts.scale</file>
8475 files, if needed, should be provided in the
8477 <file>/etc/X11/fonts/<var>fontdir</var>/<var>package</var>.<var>extension</var></file>,
8478 where <var>fontdir</var> is the name of the
8480 <file>/usr/share/fonts/X11/</file> where the
8481 package's corresponding fonts are stored
8482 (e.g., <tt>75dpi</tt> or <tt>misc</tt>),
8483 <var>package</var> is the name of the package
8484 that provides these fonts, and
8485 <var>extension</var> is either <tt>scale</tt>
8486 or <tt>alias</tt>, whichever corresponds to
8493 Font packages must declare a dependency on
8494 <tt>xfonts-utils</tt> in their control
8499 Font packages that provide one or more
8500 <file>fonts.scale</file> files as described above must
8501 invoke <prgn>update-fonts-scale</prgn> on each
8502 directory into which they installed fonts
8503 <em>before</em> invoking
8504 <prgn>update-fonts-dir</prgn> on that directory.
8505 This invocation must occur in both the
8506 <prgn>postinst</prgn> (for all arguments) and
8507 <prgn>postrm</prgn> (for all arguments except
8508 <tt>upgrade</tt>) scripts.
8512 Font packages that provide one or more
8513 <file>fonts.alias</file> files as described above must
8514 invoke <prgn>update-fonts-alias</prgn> on each
8515 directory into which they installed fonts. This
8516 invocation must occur in both the
8517 <prgn>postinst</prgn> (for all arguments) and
8518 <prgn>postrm</prgn> (for all arguments except
8519 <tt>upgrade</tt>) scripts.
8523 Font packages must invoke
8524 <prgn>update-fonts-dir</prgn> on each directory into
8525 which they installed fonts. This invocation must
8526 occur in both the <prgn>postinst</prgn> (for all
8527 arguments) and <prgn>postrm</prgn> (for all
8528 arguments except <tt>upgrade</tt>) scripts.
8532 Font packages must not provide alias names for the
8533 fonts they include which collide with alias names
8534 already in use by fonts already packaged.
8538 Font packages must not provide fonts with the same
8539 XLFD registry name as another font already packaged.
8546 <heading>Application defaults files</heading>
8549 Application defaults files must be installed in the
8550 directory <file>/etc/X11/app-defaults/</file> (use of a
8551 localized subdirectory of <file>/etc/X11/</file> as described
8552 in the <em>X Toolkit Intrinsics - C Language
8553 Interface</em> manual is also permitted). They must be
8554 registered as <tt>conffile</tt>s or handled as
8555 configuration files.
8559 Customization of programs' X resources may also be
8560 supported with the provision of a file with the same name
8561 as that of the package placed in the
8562 <file>/etc/X11/Xresources/</file> directory, which must
8563 registered as a <tt>conffile</tt> or handled as a
8564 configuration file.<footnote>
8565 Note that this mechanism is not the same as using
8566 app-defaults; app-defaults are tied to the client
8567 binary on the local file system, whereas X resources
8568 are stored in the X server and affect all connecting
8575 <heading>Installation directory issues</heading>
8578 Packages using the X Window System should not be
8579 configured to install files under the
8580 <file>/usr/X11R6/</file> directory. The
8581 <file>/usr/X11R6/</file> directory hierarchy should be
8582 regarded as obsolete.
8586 Programs that use GNU <prgn>autoconf</prgn> and
8587 <prgn>automake</prgn> are usually easily configured at
8588 compile time to use <file>/usr/</file> instead of
8589 <file>/usr/X11R6/</file>, and this should be done whenever
8590 possible. Configuration files for window managers and
8591 display managers should be placed in a subdirectory of
8592 <file>/etc/X11/</file> corresponding to the package name due
8593 to these programs' tight integration with the mechanisms
8594 of the X Window System. Application-level programs should
8595 use the <file>/etc/</file> directory unless otherwise mandated
8600 The installation of files into subdirectories
8601 of <file>/usr/X11R6/include/X11/</file> and
8602 <file>/usr/X11R6/lib/X11/</file> is now prohibited;
8603 package maintainers should determine if subdirectories of
8604 <file>/usr/lib/</file> and <file>/usr/share/</file> can be used
8609 Packages should install any relevant files into the
8610 directories <file>/usr/include/X11/</file> and
8611 <file>/usr/lib/X11/</file>, but if they do so, they must
8612 pre-depend on <tt>x11-common (>=
8613 1:7.0.0)</tt><footnote>
8615 These libraries used to be all symbolic
8616 links. However, with <tt>X11R7</tt>,
8617 <tt>/usr/include/X11</tt> and <tt>/usr/lib/X11</tt>
8618 are now real directories, and packages
8619 <strong>should</strong> ship their files here instead
8620 of in <tt>/usr/X11R6/{include,lib}/X11</tt>.
8621 <tt>x11-common (>= 1:7.0.0) </tt> is the package
8622 responsible for converting these symlinks into
8630 <heading>The OSF/Motif and OpenMotif libraries</heading>
8633 <em>Programs that require the non-DFSG-compliant OSF/Motif or
8634 OpenMotif libraries</em><footnote>
8635 OSF/Motif and OpenMotif are collectively referred to as
8636 "Motif" in this policy document.
8638 should be compiled against and tested with LessTif (a free
8639 re-implementation of Motif) instead. If the maintainer
8640 judges that the program or programs do not work
8641 sufficiently well with LessTif to be distributed and
8642 supported, but do so when compiled against Motif, then two
8643 versions of the package should be created; one linked
8644 statically against Motif and with <tt>-smotif</tt>
8645 appended to the package name, and one linked dynamically
8646 against Motif and with <tt>-dmotif</tt> appended to the
8651 Both Motif-linked versions are dependent
8652 upon non-DFSG-compliant software and thus cannot be
8653 uploaded to the <em>main</em> distribution; if the
8654 software is itself DFSG-compliant it may be uploaded to
8655 the <em>contrib</em> distribution. While known existing
8656 versions of Motif permit unlimited redistribution of
8657 binaries linked against the library (whether statically or
8658 dynamically), it is the package maintainer's
8659 responsibility to determine whether this is permitted by
8660 the license of the copy of Motif in their possession.
8666 <heading>Perl programs and modules</heading>
8669 Perl programs and modules should follow the current Perl policy.
8673 The Perl policy can be found in the <tt>perl-policy</tt>
8674 files in the <tt>debian-policy</tt> package.
8675 It is also available from the Debian web mirrors at
8676 <tt><url name="/doc/packaging-manuals/perl-policy/"
8677 id="http://www.debian.org/doc/packaging-manuals/perl-policy/"></tt>.
8682 <heading>Emacs lisp programs</heading>
8685 Please refer to the "Debian Emacs Policy" for details of how to
8686 package emacs lisp programs.
8690 The Emacs policy is available in
8691 <file>debian-emacs-policy.gz</file> of the
8692 <package>emacsen-common</package> package.
8693 It is also available from the Debian web mirrors at
8694 <tt><url name="/doc/packaging-manuals/debian-emacs-policy"
8695 id="http://www.debian.org/doc/packaging-manuals/debian-emacs-policy"></tt>.
8700 <heading>Games</heading>
8703 The permissions on <file>/var/games</file> are mode 755, owner
8704 <tt>root</tt> and group <tt>root</tt>.
8708 Each game decides on its own security policy.</p>
8711 Games which require protected, privileged access to
8712 high-score files, saved games, etc., may be made
8713 set-<em>group</em>-id (mode 2755) and owned by
8714 <tt>root:games</tt>, and use files and directories with
8715 appropriate permissions (770 <tt>root:games</tt>, for
8716 example). They must not be made
8717 set-<em>user</em>-id, as this causes security problems. (If
8718 an attacker can subvert any set-user-id game they can
8719 overwrite the executable of any other, causing other players
8720 of these games to run a Trojan horse program. With a
8721 set-group-id game the attacker only gets access to less
8722 important game data, and if they can get at the other
8723 players' accounts at all it will take considerably more
8727 Some packages, for example some fortune cookie programs, are
8728 configured by the upstream authors to install with their
8729 data files or other static information made unreadable so
8730 that they can only be accessed through set-id programs
8731 provided. You should not do this in a Debian package: anyone can
8732 download the <file>.deb</file> file and read the data from it,
8733 so there is no point making the files unreadable. Not
8734 making the files unreadable also means that you don't have
8735 to make so many programs set-id, which reduces the risk of a
8739 As described in the FHS, binaries of games should be
8740 installed in the directory <file>/usr/games</file>. This also
8741 applies to games that use the X Window System. Manual pages
8742 for games (X and non-X games) should be installed in
8743 <file>/usr/share/man/man6</file>.</p>
8749 <heading>Documentation</heading>
8752 <heading>Manual pages</heading>
8755 You should install manual pages in <prgn>nroff</prgn> source
8756 form, in appropriate places under <file>/usr/share/man</file>.
8757 You should only use sections 1 to 9 (see the FHS for more
8758 details). You must not install a pre-formatted "cat page".
8762 Each program, utility, and function should have an
8763 associated manual page included in the same package. It is
8764 suggested that all configuration files also have a manual
8765 page included as well. Manual pages for protocols and other
8766 auxiliary things are optional.
8770 If no manual page is available, this is considered as a bug
8771 and should be reported to the Debian Bug Tracking System (the
8772 maintainer of the package is allowed to write this bug report
8773 themselves, if they so desire). Do not close the bug report
8774 until a proper man page is available.<footnote>
8775 It is not very hard to write a man page. See the
8776 <url id="http://www.schweikhardt.net/man_page_howto.html"
8777 name="Man-Page-HOWTO">,
8778 <manref name="man" section="7">, the examples
8779 created by <prgn>debmake</prgn> or <prgn>dh_make</prgn>,
8780 the helper programs <prgn>help2man</prgn>, or the
8781 directory <file>/usr/share/doc/man-db/examples</file>.
8786 You may forward a complaint about a missing man page to the
8787 upstream authors, and mark the bug as forwarded in the
8788 Debian bug tracking system. Even though the GNU Project do
8789 not in general consider the lack of a man page to be a bug,
8790 we do; if they tell you that they don't consider it a bug
8791 you should leave the bug in our bug tracking system open
8796 Manual pages should be installed compressed using <tt>gzip -9</tt>.
8800 If one man page needs to be accessible via several names it
8801 is better to use a symbolic link than the <file>.so</file>
8802 feature, but there is no need to fiddle with the relevant
8803 parts of the upstream source to change from <file>.so</file> to
8804 symlinks: don't do it unless it's easy. You should not
8805 create hard links in the manual page directories, nor put
8806 absolute filenames in <file>.so</file> directives. The filename
8807 in a <file>.so</file> in a man page should be relative to the
8808 base of the man page tree (usually
8809 <file>/usr/share/man</file>). If you do not create any links
8810 (whether symlinks, hard links, or <tt>.so</tt> directives)
8811 in the file system to the alternate names of the man page,
8812 then you should not rely on <prgn>man</prgn> finding your
8813 man page under those names based solely on the information in
8814 the man page's header.<footnote>
8815 Supporting this in <prgn>man</prgn> often requires
8816 unreasonable processing time to find a manual page or to
8817 report that none exists, and moves knowledge into man's
8818 database that would be better left in the file system.
8819 This support is therefore deprecated and will cease to
8820 be present in the future.
8825 Manual pages in locale-specific subdirectories of
8826 <file>/usr/share/man</file> should use either UTF-8 or the usual
8827 legacy encoding for that language (normally the one corresponding
8828 to the shortest relevant locale name in
8829 <file>/usr/share/i18n/SUPPORTED</file>). For example, pages under
8830 <file>/usr/share/man/fr</file> should use either UTF-8 or
8831 ISO-8859-1.<footnote>
8832 <prgn>man</prgn> will automatically detect whether UTF-8 is in
8833 use. In future, all manual pages will be required to use
8839 A country name (the <tt>DE</tt> in <tt>de_DE</tt>) should not be
8840 included in the subdirectory name unless it indicates a
8841 significant difference in the language, as this excludes
8842 speakers of the language in other countries.<footnote>
8843 At the time of writing, Chinese and Portuguese are the main
8844 languages with such differences, so <file>pt_BR</file>,
8845 <file>zh_CN</file>, and <file>zh_TW</file> are all allowed.
8850 Due to limitations in current implementations, all characters
8851 in the manual page source should be representable in the usual
8852 legacy encoding for that language, even if the file is
8853 actually encoded in UTF-8. Safe alternative ways to write many
8854 characters outside that range may be found in
8855 <manref name="groff_char" section="7">.
8860 <heading>Info documents</heading>
8863 Info documents should be installed in <file>/usr/share/info</file>.
8864 They should be compressed with <tt>gzip -9</tt>.
8868 Your package should call <prgn>install-info</prgn> to update
8869 the Info <file>dir</file> file in its <prgn>postinst</prgn>
8870 script when called with a <tt>configure</tt> argument, for
8872 <example compact="compact">
8873 install-info --quiet --section Development Development \
8874 /usr/share/info/foobar.info
8878 It is a good idea to specify a section for the location of
8879 your program; this is done with the <tt>--section</tt>
8880 switch. To determine which section to use, you should look
8881 at <file>/usr/share/info/dir</file> on your system and choose the most
8882 relevant (or create a new section if none of the current
8883 sections are relevant). Note that the <tt>--section</tt>
8884 flag takes two arguments; the first is a regular expression
8885 to match (case-insensitively) against an existing section,
8886 the second is used when creating a new one.</p>
8889 You should remove the entries in the <prgn>prerm</prgn>
8890 script when called with a <tt>remove</tt> argument:
8891 <example compact="compact">
8892 install-info --quiet --remove /usr/share/info/foobar.info
8896 If <prgn>install-info</prgn> cannot find a description entry
8897 in the Info file you must supply one. See <manref
8898 name="install-info" section="8"> for details.</p>
8902 <heading>Additional documentation</heading>
8905 Any additional documentation that comes with the package may
8906 be installed at the discretion of the package maintainer.
8907 Plain text documentation should be installed in the directory
8908 <file>/usr/share/doc/<var>package</var></file>, where
8909 <var>package</var> is the name of the package, and
8910 compressed with <tt>gzip -9</tt> unless it is small.
8914 If a package comes with large amounts of documentation which
8915 many users of the package will not require you should create
8916 a separate binary package to contain it, so that it does not
8917 take up disk space on the machines of users who do not need
8918 or want it installed.</p>
8921 It is often a good idea to put text information files
8922 (<file>README</file>s, changelogs, and so forth) that come with
8923 the source package in <file>/usr/share/doc/<var>package</var></file>
8924 in the binary package. However, you don't need to install
8925 the instructions for building and installing the package, of
8929 Packages must not require the existence of any files in
8930 <file>/usr/share/doc/</file> in order to function
8932 The system administrator should be able to
8933 delete files in <file>/usr/share/doc/</file> without causing
8934 any programs to break.
8936 Any files that are referenced by programs but are also
8937 useful as stand alone documentation should be installed under
8938 <file>/usr/share/<var>package</var>/</file> with symbolic links from
8939 <file>/usr/share/doc/<var>package</var></file>.
8943 <file>/usr/share/doc/<var>package</var></file> may be a symbolic
8944 link to another directory in <file>/usr/share/doc</file> only if
8945 the two packages both come from the same source and the
8946 first package Depends on the second.<footnote>
8948 Please note that this does not override the section on
8949 changelog files below, so the file
8950 <file>/usr/share/<var>package</var>/changelog.Debian.gz</file>
8951 must refer to the changelog for the current version of
8952 <var>package</var> in question. In practice, this means
8953 that the sources of the target and the destination of the
8954 symlink must be the same (same source package and
8961 Former Debian releases placed all additional documentation
8962 in <file>/usr/doc/<var>package</var></file>. This has been
8963 changed to <file>/usr/share/doc/<var>package</var></file>,
8964 and packages must not put documentation in the directory
8965 <file>/usr/doc/<var>package</var></file>. <footnote>
8966 At this phase of the transition, we no longer require a
8967 symbolic link in <file>/usr/doc/</file>. At a later point,
8968 policy shall change to make the symbolic links a bug.
8974 <heading>Preferred documentation formats</heading>
8977 The unification of Debian documentation is being carried out
8981 If your package comes with extensive documentation in a
8982 markup format that can be converted to various other formats
8983 you should if possible ship HTML versions in a binary
8984 package, in the directory
8985 <file>/usr/share/doc/<var>appropriate-package</var></file> or
8986 its subdirectories.<footnote>
8987 The rationale: The important thing here is that HTML
8988 docs should be available in <em>some</em> package, not
8989 necessarily in the main binary package.
8994 Other formats such as PostScript may be provided at the
8995 package maintainer's discretion.
8999 <sect id="copyrightfile">
9000 <heading>Copyright information</heading>
9003 Every package must be accompanied by a verbatim copy of its
9004 copyright and distribution license in the file
9005 <file>/usr/share/doc/<var>package</var>/copyright</file>. This
9006 file must neither be compressed nor be a symbolic link.
9010 In addition, the copyright file must say where the upstream
9011 sources (if any) were obtained. It should name the original
9012 authors of the package and the Debian maintainer(s) who were
9013 involved with its creation.
9017 Packages in the <em>contrib</em> or <em>non-free</em> archive
9018 areas should state in the copyright file that the package is not
9019 part of the Debian GNU/Linux distribution and briefly explain
9024 A copy of the file which will be installed in
9025 <file>/usr/share/doc/<var>package</var>/copyright</file> should
9026 be in <file>debian/copyright</file> in the source package.
9030 <file>/usr/share/doc/<var>package</var></file> may be a symbolic
9031 link to another directory in <file>/usr/share/doc</file> only if
9032 the two packages both come from the same source and the
9033 first package Depends on the second. These rules are
9034 important because copyrights must be extractable by
9039 Packages distributed under the UCB BSD license, the Apache
9040 license (version 2.0), the Artistic license, the GNU GPL
9041 (version 2 or 3), the GNU LGPL (versions 2, 2.1, or 3), and the
9042 GNU FDL (versions 1.2 or 1.3) should refer to the corresponding
9043 files under <file>/usr/share/common-licenses</file>,<footnote>
9046 <file>/usr/share/common-licenses/BSD</file>,
9047 <file>/usr/share/common-licenses/Apache-2.0</file>,
9048 <file>/usr/share/common-licenses/Artistic</file>,
9049 <file>/usr/share/common-licenses/GPL-2</file>,
9050 <file>/usr/share/common-licenses/GPL-3</file>,
9051 <file>/usr/share/common-licenses/LGPL-2</file>,
9052 <file>/usr/share/common-licenses/LGPL-2.1</file>,
9053 <file>/usr/share/common-licenses/LGPL-3</file>,
9054 <file>/usr/share/common-licenses/GFDL-1.2</file>, and
9055 <file>/usr/share/common-licenses/GFDL-1.3</file>
9058 </footnote> rather than quoting them in the copyright
9063 You should not use the copyright file as a general <file>README</file>
9064 file. If your package has such a file it should be
9065 installed in <file>/usr/share/doc/<var>package</var>/README</file> or
9066 <file>README.Debian</file> or some other appropriate place.</p>
9070 <heading>Examples</heading>
9073 Any examples (configurations, source files, whatever),
9074 should be installed in a directory
9075 <file>/usr/share/doc/<var>package</var>/examples</file>. These
9076 files should not be referenced by any program: they're there
9077 for the benefit of the system administrator and users as
9078 documentation only. Architecture-specific example files
9079 should be installed in a directory
9080 <file>/usr/lib/<var>package</var>/examples</file> with symbolic
9082 <file>/usr/share/doc/<var>package</var>/examples</file>, or the
9083 latter directory itself may be a symbolic link to the
9088 If the purpose of a package is to provide examples, then the
9089 example files may be installed into
9090 <file>/usr/share/doc/<var>package</var></file>.
9094 <sect id="changelogs">
9095 <heading>Changelog files</heading>
9098 Packages that are not Debian-native must contain a
9099 compressed copy of the <file>debian/changelog</file> file from
9100 the Debian source tree in
9101 <file>/usr/share/doc/<var>package</var></file> with the name
9102 <file>changelog.Debian.gz</file>.
9106 If an upstream changelog is available, it should be accessible as
9107 <file>/usr/share/doc/<var>package</var>/changelog.gz</file> in
9108 plain text. If the upstream changelog is distributed in
9109 HTML, it should be made available in that form as
9110 <file>/usr/share/doc/<var>package</var>/changelog.html.gz</file>
9111 and a plain text <file>changelog.gz</file> should be generated
9112 from it using, for example, <tt>lynx -dump -nolist</tt>. If
9113 the upstream changelog files do not already conform to this
9114 naming convention, then this may be achieved either by
9115 renaming the files, or by adding a symbolic link, at the
9116 maintainer's discretion.<footnote>
9117 Rationale: People should not have to look in places for
9118 upstream changelogs merely because they are given
9119 different names or are distributed in HTML format.
9124 All of these files should be installed compressed using
9125 <tt>gzip -9</tt>, as they will become large with time even
9126 if they start out small.
9130 If the package has only one changelog which is used both as
9131 the Debian changelog and the upstream one because there is
9132 no separate upstream maintainer then that changelog should
9133 usually be installed as
9134 <file>/usr/share/doc/<var>package</var>/changelog.gz</file>; if
9135 there is a separate upstream maintainer, but no upstream
9136 changelog, then the Debian changelog should still be called
9137 <file>changelog.Debian.gz</file>.
9141 For details about the format and contents of the Debian
9142 changelog file, please see <ref id="dpkgchangelog">.
9147 <appendix id="pkg-scope">
9148 <heading>Introduction and scope of these appendices</heading>
9151 These appendices are taken essentially verbatim from the
9152 now-deprecated Packaging Manual, version 3.2.1.0. They are
9153 the chapters which are likely to be of use to package
9154 maintainers and which have not already been included in the
9155 policy document itself. Most of these sections are very likely
9156 not relevant to policy; they should be treated as
9157 documentation for the packaging system. Please note that these
9158 appendices are included for convenience, and for historical
9159 reasons: they used to be part of policy package, and they have
9160 not yet been incorporated into dpkg documentation. However,
9161 they still have value, and hence they are presented here.
9165 They have not yet been checked to ensure that they are
9166 compatible with the contents of policy, and if there are any
9167 contradictions, the version in the main policy document takes
9168 precedence. The remaining chapters of the old Packaging
9169 Manual have also not been read in detail to ensure that there
9170 are not parts which have been left out. Both of these will be
9175 Certain parts of the Packaging manual were integrated into the
9176 Policy Manual proper, and removed from the appendices. Links
9177 have been placed from the old locations to the new ones.
9181 <prgn>dpkg</prgn> is a suite of programs for creating binary
9182 package files and installing and removing them on Unix
9184 <prgn>dpkg</prgn> is targeted primarily at Debian
9185 GNU/Linux, but may work on or be ported to other
9191 The binary packages are designed for the management of
9192 installed executable programs (usually compiled binaries) and
9193 their associated data, though source code examples and
9194 documentation are provided as part of some packages.</p>
9197 This manual describes the technical aspects of creating Debian
9198 binary packages (<file>.deb</file> files). It documents the
9199 behavior of the package management programs
9200 <prgn>dpkg</prgn>, <prgn>dselect</prgn> et al. and the way
9201 they interact with packages.</p>
9204 It also documents the interaction between
9205 <prgn>dselect</prgn>'s core and the access method scripts it
9206 uses to actually install the selected packages, and describes
9207 how to create a new access method.</p>
9210 This manual does not go into detail about the options and
9211 usage of the package building and installation tools. It
9212 should therefore be read in conjunction with those programs'
9217 The utility programs which are provided with <prgn>dpkg</prgn>
9218 for managing various system configuration and similar issues,
9219 such as <prgn>update-rc.d</prgn> and
9220 <prgn>install-info</prgn>, are not described in detail here -
9221 please see their man pages.
9225 It is assumed that the reader is reasonably familiar with the
9226 <prgn>dpkg</prgn> System Administrators' manual.
9227 Unfortunately this manual does not yet exist.
9231 The Debian version of the FSF's GNU hello program is provided
9232 as an example for people wishing to create Debian
9233 packages. The Debian <prgn>debmake</prgn> package is
9234 recommended as a very helpful tool in creating and maintaining
9235 Debian packages. However, while the tools and examples are
9236 helpful, they do not replace the need to read and follow the
9237 Policy and Programmer's Manual.</p>
9240 <appendix id="pkg-binarypkg">
9241 <heading>Binary packages (from old Packaging Manual)</heading>
9244 The binary package has two main sections. The first part
9245 consists of various control information files and scripts used
9246 by <prgn>dpkg</prgn> when installing and removing. See <ref
9247 id="pkg-controlarea">.
9251 The second part is an archive containing the files and
9252 directories to be installed.
9256 In the future binary packages may also contain other
9257 components, such as checksums and digital signatures. The
9258 format for the archive is described in full in the
9259 <file>deb(5)</file> man page.
9263 <sect id="pkg-bincreating"><heading>Creating package files -
9264 <prgn>dpkg-deb</prgn>
9268 All manipulation of binary package files is done by
9269 <prgn>dpkg-deb</prgn>; it's the only program that has
9270 knowledge of the format. (<prgn>dpkg-deb</prgn> may be
9271 invoked by calling <prgn>dpkg</prgn>, as <prgn>dpkg</prgn>
9272 will spot that the options requested are appropriate to
9273 <prgn>dpkg-deb</prgn> and invoke that instead with the same
9278 In order to create a binary package you must make a
9279 directory tree which contains all the files and directories
9280 you want to have in the file system data part of the package.
9281 In Debian-format source packages this directory is usually
9282 <file>debian/tmp</file>, relative to the top of the package's
9287 They should have the locations (relative to the root of the
9288 directory tree you're constructing) ownerships and
9289 permissions which you want them to have on the system when
9294 With current versions of <prgn>dpkg</prgn> the uid/username
9295 and gid/groupname mappings for the users and groups being
9296 used should be the same on the system where the package is
9297 built and the one where it is installed.
9301 You need to add one special directory to the root of the
9302 miniature file system tree you're creating:
9303 <prgn>DEBIAN</prgn>. It should contain the control
9304 information files, notably the binary package control file
9305 (see <ref id="pkg-controlfile">).
9309 The <prgn>DEBIAN</prgn> directory will not appear in the
9310 file system archive of the package, and so won't be installed
9311 by <prgn>dpkg</prgn> when the package is installed.
9315 When you've prepared the package, you should invoke:
9317 dpkg --build <var>directory</var>
9322 This will build the package in
9323 <file><var>directory</var>.deb</file>. (<prgn>dpkg</prgn> knows
9324 that <tt>--build</tt> is a <prgn>dpkg-deb</prgn> option, so
9325 it invokes <prgn>dpkg-deb</prgn> with the same arguments to
9330 See the man page <manref name="dpkg-deb" section="8"> for details of how
9331 to examine the contents of this newly-created file. You may find the
9332 output of following commands enlightening:
9334 dpkg-deb --info <var>filename</var>.deb
9335 dpkg-deb --contents <var>filename</var>.deb
9336 dpkg --contents <var>filename</var>.deb
9338 To view the copyright file for a package you could use this command:
9340 dpkg --fsys-tarfile <var>filename</var>.deb | tar xOf - --wildcards \*/copyright | pager
9345 <sect id="pkg-controlarea">
9346 <heading>Package control information files</heading>
9349 The control information portion of a binary package is a
9350 collection of files with names known to <prgn>dpkg</prgn>.
9351 It will treat the contents of these files specially - some
9352 of them contain information used by <prgn>dpkg</prgn> when
9353 installing or removing the package; others are scripts which
9354 the package maintainer wants <prgn>dpkg</prgn> to run.
9358 It is possible to put other files in the package control
9359 area, but this is not generally a good idea (though they
9360 will largely be ignored).
9364 Here is a brief list of the control info files supported by
9365 <prgn>dpkg</prgn> and a summary of what they're used for.
9370 <tag><tt>control</tt>
9373 This is the key description file used by
9374 <prgn>dpkg</prgn>. It specifies the package's name
9375 and version, gives its description for the user,
9376 states its relationships with other packages, and so
9377 forth. See <ref id="sourcecontrolfiles"> and
9378 <ref id="binarycontrolfiles">.
9382 It is usually generated automatically from information
9383 in the source package by the
9384 <prgn>dpkg-gencontrol</prgn> program, and with
9385 assistance from <prgn>dpkg-shlibdeps</prgn>.
9386 See <ref id="pkg-sourcetools">.
9390 <tag><tt>postinst</tt>, <tt>preinst</tt>, <tt>postrm</tt>,
9395 These are executable files (usually scripts) which
9396 <prgn>dpkg</prgn> runs during installation, upgrade
9397 and removal of packages. They allow the package to
9398 deal with matters which are particular to that package
9399 or require more complicated processing than that
9400 provided by <prgn>dpkg</prgn>. Details of when and
9401 how they are called are in <ref id="maintainerscripts">.
9405 It is very important to make these scripts idempotent.
9406 See <ref id="idempotency">.
9410 The maintainer scripts are guaranteed to run with a
9411 controlling terminal and can interact with the user.
9412 See <ref id="controllingterminal">.
9416 <tag><tt>conffiles</tt>
9419 This file contains a list of configuration files which
9420 are to be handled automatically by <prgn>dpkg</prgn>
9421 (see <ref id="pkg-conffiles">). Note that not necessarily
9422 every configuration file should be listed here.
9425 <tag><tt>shlibs</tt>
9428 This file contains a list of the shared libraries
9429 supplied by the package, with dependency details for
9430 each. This is used by <prgn>dpkg-shlibdeps</prgn>
9431 when it determines what dependencies are required in a
9432 package control file. The <tt>shlibs</tt> file format
9433 is described on <ref id="shlibs">.
9438 <sect id="pkg-controlfile">
9439 <heading>The main control information file: <tt>control</tt></heading>
9442 The most important control information file used by
9443 <prgn>dpkg</prgn> when it installs a package is
9444 <tt>control</tt>. It contains all the package's "vital
9449 The binary package control files of packages built from
9450 Debian sources are made by a special tool,
9451 <prgn>dpkg-gencontrol</prgn>, which reads
9452 <file>debian/control</file> and <file>debian/changelog</file> to
9453 find the information it needs. See <ref id="pkg-sourcepkg"> for
9458 The fields in binary package control files are listed in
9459 <ref id="binarycontrolfiles">.
9463 A description of the syntax of control files and the purpose
9464 of the fields is available in <ref id="controlfields">.
9469 <heading>Time Stamps</heading>
9472 See <ref id="timestamps">.
9477 <appendix id="pkg-sourcepkg">
9478 <heading>Source packages (from old Packaging Manual) </heading>
9481 The Debian binary packages in the distribution are generated
9482 from Debian sources, which are in a special format to assist
9483 the easy and automatic building of binaries.
9486 <sect id="pkg-sourcetools">
9487 <heading>Tools for processing source packages</heading>
9490 Various tools are provided for manipulating source packages;
9491 they pack and unpack sources and help build of binary
9492 packages and help manage the distribution of new versions.
9496 They are introduced and typical uses described here; see
9497 <manref name="dpkg-source" section="1"> for full
9498 documentation about their arguments and operation.
9502 For examples of how to construct a Debian source package,
9503 and how to use those utilities that are used by Debian
9504 source packages, please see the <prgn>hello</prgn> example
9508 <sect1 id="pkg-dpkg-source">
9510 <prgn>dpkg-source</prgn> - packs and unpacks Debian source
9515 This program is frequently used by hand, and is also
9516 called from package-independent automated building scripts
9517 such as <prgn>dpkg-buildpackage</prgn>.
9521 To unpack a package it is typically invoked with
9523 dpkg-source -x <var>.../path/to/filename</var>.dsc
9528 with the <file><var>filename</var>.tar.gz</file> and
9529 <file><var>filename</var>.diff.gz</file> (if applicable) in
9530 the same directory. It unpacks into
9531 <file><var>package</var>-<var>version</var></file>, and if
9533 <file><var>package</var>-<var>version</var>.orig</file>, in
9534 the current directory.
9538 To create a packed source archive it is typically invoked:
9540 dpkg-source -b <var>package</var>-<var>version</var>
9545 This will create the <file>.dsc</file>, <file>.tar.gz</file> and
9546 <file>.diff.gz</file> (if appropriate) in the current
9547 directory. <prgn>dpkg-source</prgn> does not clean the
9548 source tree first - this must be done separately if it is
9553 See also <ref id="pkg-sourcearchives">.</p>
9557 <sect1 id="pkg-dpkg-buildpackage">
9559 <prgn>dpkg-buildpackage</prgn> - overall package-building
9564 <prgn>dpkg-buildpackage</prgn> is a script which invokes
9565 <prgn>dpkg-source</prgn>, the <file>debian/rules</file>
9566 targets <tt>clean</tt>, <tt>build</tt> and
9567 <tt>binary</tt>, <prgn>dpkg-genchanges</prgn> and
9568 <prgn>gpg</prgn> (or <prgn>pgp</prgn>) to build a signed
9569 source and binary package upload.
9573 It is usually invoked by hand from the top level of the
9574 built or unbuilt source directory. It may be invoked with
9575 no arguments; useful arguments include:
9576 <taglist compact="compact">
9577 <tag><tt>-uc</tt>, <tt>-us</tt></tag>
9580 Do not sign the <tt>.changes</tt> file or the
9581 source package <tt>.dsc</tt> file, respectively.</p>
9583 <tag><tt>-p<var>sign-command</var></tt></tag>
9586 Invoke <var>sign-command</var> instead of finding
9587 <tt>gpg</tt> or <tt>pgp</tt> on the <prgn>PATH</prgn>.
9588 <var>sign-command</var> must behave just like
9589 <prgn>gpg</prgn> or <tt>pgp</tt>.</p>
9591 <tag><tt>-r<var>root-command</var></tt></tag>
9594 When root privilege is required, invoke the command
9595 <var>root-command</var>. <var>root-command</var>
9596 should invoke its first argument as a command, from
9597 the <prgn>PATH</prgn> if necessary, and pass its
9598 second and subsequent arguments to the command it
9599 calls. If no <var>root-command</var> is supplied
9600 then <var>dpkg-buildpackage</var> will take no
9601 special action to gain root privilege, so that for
9602 most packages it will have to be invoked as root to
9605 <tag><tt>-b</tt>, <tt>-B</tt></tag>
9608 Two types of binary-only build and upload - see
9609 <manref name="dpkg-source" section="1">.
9616 <sect1 id="pkg-dpkg-gencontrol">
9618 <prgn>dpkg-gencontrol</prgn> - generates binary package
9623 This program is usually called from <file>debian/rules</file>
9624 (see <ref id="pkg-sourcetree">) in the top level of the source
9629 This is usually done just before the files and directories in the
9630 temporary directory tree where the package is being built have their
9631 permissions and ownerships set and the package is constructed using
9632 <prgn>dpkg-deb/</prgn>
9634 This is so that the control file which is produced has
9635 the right permissions
9640 <prgn>dpkg-gencontrol</prgn> must be called after all the
9641 files which are to go into the package have been placed in
9642 the temporary build directory, so that its calculation of
9643 the installed size of a package is correct.
9647 It is also necessary for <prgn>dpkg-gencontrol</prgn> to
9648 be run after <prgn>dpkg-shlibdeps</prgn> so that the
9649 variable substitutions created by
9650 <prgn>dpkg-shlibdeps</prgn> in <file>debian/substvars</file>
9655 For a package which generates only one binary package, and
9656 which builds it in <file>debian/tmp</file> relative to the top
9657 of the source package, it is usually sufficient to call
9658 <prgn>dpkg-gencontrol</prgn>.
9662 Sources which build several binaries will typically need
9665 dpkg-gencontrol -Pdebian/tmp-<var>pkg</var> -p<var>package</var>
9666 </example> The <tt>-P</tt> tells
9667 <prgn>dpkg-gencontrol</prgn> that the package is being
9668 built in a non-default directory, and the <tt>-p</tt>
9669 tells it which package's control file should be generated.
9673 <prgn>dpkg-gencontrol</prgn> also adds information to the
9674 list of files in <file>debian/files</file>, for the benefit of
9675 (for example) a future invocation of
9676 <prgn>dpkg-genchanges</prgn>.</p>
9679 <sect1 id="pkg-dpkg-shlibdeps">
9681 <prgn>dpkg-shlibdeps</prgn> - calculates shared library
9686 This program is usually called from <file>debian/rules</file>
9687 just before <prgn>dpkg-gencontrol</prgn> (see <ref
9688 id="pkg-sourcetree">), in the top level of the source tree.
9692 Its arguments are executables and shared libraries
9695 They may be specified either in the locations in the
9696 source tree where they are created or in the locations
9697 in the temporary build tree where they are installed
9698 prior to binary package creation.
9700 </footnote> for which shared library dependencies should
9701 be included in the binary package's control file.
9705 If some of the found shared libraries should only
9706 warrant a <tt>Recommends</tt> or <tt>Suggests</tt>, or if
9707 some warrant a <tt>Pre-Depends</tt>, this can be achieved
9708 by using the <tt>-d<var>dependency-field</var></tt> option
9709 before those executable(s). (Each <tt>-d</tt> option
9710 takes effect until the next <tt>-d</tt>.)
9714 <prgn>dpkg-shlibdeps</prgn> does not directly cause the
9715 output control file to be modified. Instead by default it
9716 adds to the <file>debian/substvars</file> file variable
9717 settings like <tt>shlibs:Depends</tt>. These variable
9718 settings must be referenced in dependency fields in the
9719 appropriate per-binary-package sections of the source
9724 For example, a package that generates an essential part
9725 which requires dependencies, and optional parts that
9726 which only require a recommendation, would separate those
9727 two sets of dependencies into two different fields.<footnote>
9728 At the time of writing, an example for this was the
9729 <package/xmms/ package, with Depends used for the xmms
9730 executable, Recommends for the plug-ins and Suggests for
9731 even more optional features provided by unzip.
9733 It can say in its <file>debian/rules</file>:
9735 dpkg-shlibdeps -dDepends <var>program anotherprogram ...</var> \
9736 -dRecommends <var>optionalpart anotheroptionalpart</var>
9738 and then in its main control file <file>debian/control</file>:
9741 Depends: ${shlibs:Depends}
9742 Recommends: ${shlibs:Recommends}
9748 Sources which produce several binary packages with
9749 different shared library dependency requirements can use
9750 the <tt>-p<var>varnameprefix</var></tt> option to override
9751 the default <tt>shlibs:</tt> prefix (one invocation of
9752 <prgn>dpkg-shlibdeps</prgn> per setting of this option).
9753 They can thus produce several sets of dependency
9754 variables, each of the form
9755 <tt><var>varnameprefix</var>:<var>dependencyfield</var></tt>,
9756 which can be referred to in the appropriate parts of the
9757 binary package control files.
9762 <sect1 id="pkg-dpkg-distaddfile">
9764 <prgn>dpkg-distaddfile</prgn> - adds a file to
9765 <file>debian/files</file>
9769 Some packages' uploads need to include files other than
9770 the source and binary package files.
9774 <prgn>dpkg-distaddfile</prgn> adds a file to the
9775 <file>debian/files</file> file so that it will be included in
9776 the <file>.changes</file> file when
9777 <prgn>dpkg-genchanges</prgn> is run.
9781 It is usually invoked from the <tt>binary</tt> target of
9782 <file>debian/rules</file>:
9784 dpkg-distaddfile <var>filename</var> <var>section</var> <var>priority</var>
9786 The <var>filename</var> is relative to the directory where
9787 <prgn>dpkg-genchanges</prgn> will expect to find it - this
9788 is usually the directory above the top level of the source
9789 tree. The <file>debian/rules</file> target should put the
9790 file there just before or just after calling
9791 <prgn>dpkg-distaddfile</prgn>.
9795 The <var>section</var> and <var>priority</var> are passed
9796 unchanged into the resulting <file>.changes</file> file.
9801 <sect1 id="pkg-dpkg-genchanges">
9803 <prgn>dpkg-genchanges</prgn> - generates a <file>.changes</file>
9808 This program is usually called by package-independent
9809 automatic building scripts such as
9810 <prgn>dpkg-buildpackage</prgn>, but it may also be called
9815 It is usually called in the top level of a built source
9816 tree, and when invoked with no arguments will print out a
9817 straightforward <file>.changes</file> file based on the
9818 information in the source package's changelog and control
9819 file and the binary and source packages which should have
9825 <sect1 id="pkg-dpkg-parsechangelog">
9827 <prgn>dpkg-parsechangelog</prgn> - produces parsed
9828 representation of a changelog
9832 This program is used internally by
9833 <prgn>dpkg-source</prgn> et al. It may also occasionally
9834 be useful in <file>debian/rules</file> and elsewhere. It
9835 parses a changelog, <file>debian/changelog</file> by default,
9836 and prints a control-file format representation of the
9837 information in it to standard output.
9841 <sect1 id="pkg-dpkg-architecture">
9843 <prgn>dpkg-architecture</prgn> - information about the build and
9848 This program can be used manually, but is also invoked by
9849 <tt>dpkg-buildpackage</tt> or <file>debian/rules</file> to set
9850 environment or make variables which specify the build and host
9851 architecture for the package building process.
9856 <sect id="pkg-sourcetree">
9857 <heading>The Debianised source tree</heading>
9860 The source archive scheme described later is intended to
9861 allow a Debianised source tree with some associated control
9862 information to be reproduced and transported easily. The
9863 Debianised source tree is a version of the original program
9864 with certain files added for the benefit of the
9865 Debianisation process, and with any other changes required
9866 made to the rest of the source code and installation
9871 The extra files created for Debian are in the subdirectory
9872 <file>debian</file> of the top level of the Debianised source
9873 tree. They are described below.
9876 <sect1 id="pkg-debianrules">
9877 <heading><file>debian/rules</file> - the main building script</heading>
9880 See <ref id="debianrules">.
9885 <sect1 id="pkg-dpkgchangelog">
9886 <heading><file>debian/changelog</file></heading>
9889 See <ref id="dpkgchangelog">.
9892 <sect2><heading>Defining alternative changelog formats
9896 It is possible to use a different format to the standard
9897 one, by providing a parser for the format you wish to
9902 In order to have <tt>dpkg-parsechangelog</tt> run your
9903 parser, you must include a line within the last 40 lines
9904 of your file matching the Perl regular expression:
9905 <tt>\schangelog-format:\s+([0-9a-z]+)\W</tt> The part in
9906 parentheses should be the name of the format. For
9907 example, you might say:
9909 @@@ changelog-format: joebloggs @@@
9911 Changelog format names are non-empty strings of alphanumerics.
9915 If such a line exists then <tt>dpkg-parsechangelog</tt>
9916 will look for the parser as
9917 <file>/usr/lib/dpkg/parsechangelog/<var>format-name</var></file>
9919 <file>/usr/local/lib/dpkg/parsechangelog/<var>format-name</var></file>;
9920 it is an error for it not to find it, or for it not to
9921 be an executable program. The default changelog format
9922 is <tt>dpkg</tt>, and a parser for it is provided with
9923 the <tt>dpkg</tt> package.
9927 The parser will be invoked with the changelog open on
9928 standard input at the start of the file. It should read
9929 the file (it may seek if it wishes) to determine the
9930 information required and return the parsed information
9931 to standard output in the form of a series of control
9932 fields in the standard format. By default it should
9933 return information about only the most recent version in
9934 the changelog; it should accept a
9935 <tt>-v<var>version</var></tt> option to return changes
9936 information from all versions present <em>strictly
9937 after</em> <var>version</var>, and it should then be an
9938 error for <var>version</var> not to be present in the
9944 <list compact="compact">
9945 <item><qref id="f-Source"><tt>Source</tt></qref></item>
9946 <item><qref id="f-Version"><tt>Version</tt></qref> (mandatory)</item>
9947 <item><qref id="f-Distribution"><tt>Distribution</tt></qref> (mandatory)</item>
9948 <item><qref id="f-Urgency"><tt>Urgency</tt></qref> (mandatory)</item>
9949 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
9950 <item><qref id="f-Date"><tt>Date</tt></qref></item>
9951 <item><qref id="f-Changes"><tt>Changes</tt></qref> (mandatory)</item>
9956 If several versions are being returned (due to the use
9957 of <tt>-v</tt>), the urgency value should be of the
9958 highest urgency code listed at the start of any of the
9959 versions requested followed by the concatenated
9960 (space-separated) comments from all the versions
9961 requested; the maintainer, version, distribution and
9962 date should always be from the most recent version.
9966 For the format of the <tt>Changes</tt> field see
9967 <ref id="f-Changes">.
9971 If the changelog format which is being parsed always or
9972 almost always leaves a blank line between individual
9973 change notes these blank lines should be stripped out,
9974 so as to make the resulting output compact.
9978 If the changelog format does not contain date or package
9979 name information this information should be omitted from
9980 the output. The parser should not attempt to synthesize
9981 it or find it from other sources.
9985 If the changelog does not have the expected format the
9986 parser should exit with a nonzero exit status, rather
9987 than trying to muddle through and possibly generating
9992 A changelog parser may not interact with the user at
9998 <sect1 id="pkg-srcsubstvars">
9999 <heading><file>debian/substvars</file> and variable substitutions</heading>
10002 See <ref id="substvars">.
10008 <heading><file>debian/files</file></heading>
10011 See <ref id="debianfiles">.
10015 <sect1><heading><file>debian/tmp</file>
10019 This is the canonical temporary location for the
10020 construction of binary packages by the <tt>binary</tt>
10021 target. The directory <file>tmp</file> serves as the root of
10022 the file system tree as it is being constructed (for
10023 example, by using the package's upstream makefiles install
10024 targets and redirecting the output there), and it also
10025 contains the <tt>DEBIAN</tt> subdirectory. See <ref
10026 id="pkg-bincreating">.
10030 If several binary packages are generated from the same
10031 source tree it is usual to use several
10032 <file>debian/tmp<var>something</var></file> directories, for
10033 example <file>tmp-a</file> or <file>tmp-doc</file>.
10037 Whatever <file>tmp</file> directories are created and used by
10038 <tt>binary</tt> must of course be removed by the
10039 <tt>clean</tt> target.</p></sect1>
10043 <sect id="pkg-sourcearchives"><heading>Source packages as archives
10047 As it exists on the FTP site, a Debian source package
10048 consists of three related files. You must have the right
10049 versions of all three to be able to use them.
10054 <tag>Debian source control file - <tt>.dsc</tt></tag>
10056 This file is a control file used by <prgn>dpkg-source</prgn>
10057 to extract a source package.
10058 See <ref id="debiansourcecontrolfiles">.
10062 Original source archive -
10064 <var>package</var>_<var>upstream-version</var>.orig.tar.gz
10070 This is a compressed (with <tt>gzip -9</tt>)
10071 <prgn>tar</prgn> file containing the source code from
10072 the upstream authors of the program.
10077 Debianisation diff -
10079 <var>package</var>_<var>upstream_version-revision</var>.diff.gz
10085 This is a unified context diff (<tt>diff -u</tt>)
10086 giving the changes which are required to turn the
10087 original source into the Debian source. These changes
10088 may only include editing and creating plain files.
10089 The permissions of files, the targets of symbolic
10090 links and the characteristics of special files or
10091 pipes may not be changed and no files may be removed
10096 All the directories in the diff must exist, except the
10097 <file>debian</file> subdirectory of the top of the source
10098 tree, which will be created by
10099 <prgn>dpkg-source</prgn> if necessary when unpacking.
10103 The <prgn>dpkg-source</prgn> program will
10104 automatically make the <file>debian/rules</file> file
10105 executable (see below).</p></item>
10110 If there is no original source code - for example, if the
10111 package is specially prepared for Debian or the Debian
10112 maintainer is the same as the upstream maintainer - the
10113 format is slightly different: then there is no diff, and the
10115 <file><var>package</var>_<var>version</var>.tar.gz</file>,
10116 and preferably contains a directory named
10117 <file><var>package</var>-<var>version</var></file>.
10122 <heading>Unpacking a Debian source package without <prgn>dpkg-source</prgn></heading>
10125 <tt>dpkg-source -x</tt> is the recommended way to unpack a
10126 Debian source package. However, if it is not available it
10127 is possible to unpack a Debian source archive as follows:
10128 <enumlist compact="compact">
10131 Untar the tarfile, which will create a <file>.orig</file>
10135 <p>Rename the <file>.orig</file> directory to
10136 <file><var>package</var>-<var>version</var></file>.</p>
10140 Create the subdirectory <file>debian</file> at the top of
10141 the source tree.</p>
10143 <item><p>Apply the diff using <tt>patch -p0</tt>.</p>
10145 <item><p>Untar the tarfile again if you want a copy of the original
10146 source code alongside the Debianised version.</p>
10151 It is not possible to generate a valid Debian source archive
10152 without using <prgn>dpkg-source</prgn>. In particular,
10153 attempting to use <prgn>diff</prgn> directly to generate the
10154 <file>.diff.gz</file> file will not work.
10158 <heading>Restrictions on objects in source packages</heading>
10161 The source package may not contain any hard links
10163 This is not currently detected when building source
10164 packages, but only when extracting
10168 Hard links may be permitted at some point in the
10169 future, but would require a fair amount of
10171 </footnote>, device special files, sockets or setuid or
10174 Setgid directories are allowed.
10179 The source packaging tools manage the changes between the
10180 original and Debianised source using <prgn>diff</prgn> and
10181 <prgn>patch</prgn>. Turning the original source tree as
10182 included in the <file>.orig.tar.gz</file> into the debianised
10183 source must not involve any changes which cannot be
10184 handled by these tools. Problematic changes which cause
10185 <prgn>dpkg-source</prgn> to halt with an error when
10186 building the source package are:
10187 <list compact="compact">
10188 <item><p>Adding or removing symbolic links, sockets or pipes.</p>
10190 <item><p>Changing the targets of symbolic links.</p>
10192 <item><p>Creating directories, other than <file>debian</file>.</p>
10194 <item><p>Changes to the contents of binary files.</p></item>
10195 </list> Changes which cause <prgn>dpkg-source</prgn> to
10196 print a warning but continue anyway are:
10197 <list compact="compact">
10200 Removing files, directories or symlinks.
10202 Renaming a file is not treated specially - it is
10203 seen as the removal of the old file (which
10204 generates a warning, but is otherwise ignored),
10205 and the creation of the new one.
10211 Changed text files which are missing the usual final
10212 newline (either in the original or the modified
10217 Changes which are not represented, but which are not detected by
10218 <prgn>dpkg-source</prgn>, are:
10219 <list compact="compact">
10220 <item><p>Changing the permissions of files (other than
10221 <file>debian/rules</file>) and directories.</p></item>
10226 The <file>debian</file> directory and <file>debian/rules</file>
10227 are handled specially by <prgn>dpkg-source</prgn> - before
10228 applying the changes it will create the <file>debian</file>
10229 directory, and afterwards it will make
10230 <file>debian/rules</file> world-executable.
10236 <appendix id="pkg-controlfields">
10237 <heading>Control files and their fields (from old Packaging Manual)</heading>
10240 Many of the tools in the <prgn>dpkg</prgn> suite manipulate
10241 data in a common format, known as control files. Binary and
10242 source packages have control data as do the <file>.changes</file>
10243 files which control the installation of uploaded files, and
10244 <prgn>dpkg</prgn>'s internal databases are in a similar
10249 <heading>Syntax of control files</heading>
10252 See <ref id="controlsyntax">.
10256 It is important to note that there are several fields which
10257 are optional as far as <prgn>dpkg</prgn> and the related
10258 tools are concerned, but which must appear in every Debian
10259 package, or whose omission may cause problems.
10264 <heading>List of fields</heading>
10267 See <ref id="controlfieldslist">.
10271 This section now contains only the fields that didn't belong
10272 to the Policy manual.
10275 <sect1 id="pkg-f-Filename">
10276 <heading><tt>Filename</tt> and <tt>MSDOS-Filename</tt></heading>
10279 These fields in <tt>Packages</tt> files give the
10280 filename(s) of (the parts of) a package in the
10281 distribution directories, relative to the root of the
10282 Debian hierarchy. If the package has been split into
10283 several parts the parts are all listed in order, separated
10288 <sect1 id="pkg-f-Size">
10289 <heading><tt>Size</tt> and <tt>MD5sum</tt></heading>
10292 These fields in <file>Packages</file> files give the size (in
10293 bytes, expressed in decimal) and MD5 checksum of the
10294 file(s) which make(s) up a binary package in the
10295 distribution. If the package is split into several parts
10296 the values for the parts are listed in order, separated by
10301 <sect1 id="pkg-f-Status">
10302 <heading><tt>Status</tt></heading>
10305 This field in <prgn>dpkg</prgn>'s status file records
10306 whether the user wants a package installed, removed or
10307 left alone, whether it is broken (requiring
10308 re-installation) or not and what its current state on the
10309 system is. Each of these pieces of information is a
10314 <sect1 id="pkg-f-Config-Version">
10315 <heading><tt>Config-Version</tt></heading>
10318 If a package is not installed or not configured, this
10319 field in <prgn>dpkg</prgn>'s status file records the last
10320 version of the package which was successfully
10325 <sect1 id="pkg-f-Conffiles">
10326 <heading><tt>Conffiles</tt></heading>
10329 This field in <prgn>dpkg</prgn>'s status file contains
10330 information about the automatically-managed configuration
10331 files held by a package. This field should <em>not</em>
10332 appear anywhere in a package!
10337 <heading>Obsolete fields</heading>
10340 These are still recognized by <prgn>dpkg</prgn> but should
10341 not appear anywhere any more.
10343 <taglist compact="compact">
10345 <tag><tt>Revision</tt></tag>
10346 <tag><tt>Package-Revision</tt></tag>
10347 <tag><tt>Package_Revision</tt></tag>
10349 The Debian revision part of the package version was
10350 at one point in a separate control file field. This
10351 field went through several names.
10354 <tag><tt>Recommended</tt></tag>
10355 <item>Old name for <tt>Recommends</tt>.</item>
10357 <tag><tt>Optional</tt></tag>
10358 <item>Old name for <tt>Suggests</tt>.</item>
10360 <tag><tt>Class</tt></tag>
10361 <item>Old name for <tt>Priority</tt>.</item>
10370 <appendix id="pkg-conffiles">
10371 <heading>Configuration file handling (from old Packaging Manual)</heading>
10374 <prgn>dpkg</prgn> can do a certain amount of automatic
10375 handling of package configuration files.
10379 Whether this mechanism is appropriate depends on a number of
10380 factors, but basically there are two approaches to any
10381 particular configuration file.
10385 The easy method is to ship a best-effort configuration in the
10386 package, and use <prgn>dpkg</prgn>'s conffile mechanism to
10387 handle updates. If the user is unlikely to want to edit the
10388 file, but you need them to be able to without losing their
10389 changes, and a new package with a changed version of the file
10390 is only released infrequently, this is a good approach.
10394 The hard method is to build the configuration file from
10395 scratch in the <prgn>postinst</prgn> script, and to take the
10396 responsibility for fixing any mistakes made in earlier
10397 versions of the package automatically. This will be
10398 appropriate if the file is likely to need to be different on
10402 <sect><heading>Automatic handling of configuration files by
10407 A package may contain a control area file called
10408 <tt>conffiles</tt>. This file should be a list of filenames
10409 of configuration files needing automatic handling, separated
10410 by newlines. The filenames should be absolute pathnames,
10411 and the files referred to should actually exist in the
10416 When a package is upgraded <prgn>dpkg</prgn> will process
10417 the configuration files during the configuration stage,
10418 shortly before it runs the package's <prgn>postinst</prgn>
10423 For each file it checks to see whether the version of the
10424 file included in the package is the same as the one that was
10425 included in the last version of the package (the one that is
10426 being upgraded from); it also compares the version currently
10427 installed on the system with the one shipped with the last
10432 If neither the user nor the package maintainer has changed
10433 the file, it is left alone. If one or the other has changed
10434 their version, then the changed version is preferred - i.e.,
10435 if the user edits their file, but the package maintainer
10436 doesn't ship a different version, the user's changes will
10437 stay, silently, but if the maintainer ships a new version
10438 and the user hasn't edited it the new version will be
10439 installed (with an informative message). If both have
10440 changed their version the user is prompted about the problem
10441 and must resolve the differences themselves.
10445 The comparisons are done by calculating the MD5 message
10446 digests of the files, and storing the MD5 of the file as it
10447 was included in the most recent version of the package.
10451 When a package is installed for the first time
10452 <prgn>dpkg</prgn> will install the file that comes with it,
10453 unless that would mean overwriting a file already on the
10458 However, note that <prgn>dpkg</prgn> will <em>not</em>
10459 replace a conffile that was removed by the user (or by a
10460 script). This is necessary because with some programs a
10461 missing file produces an effect hard or impossible to
10462 achieve in another way, so that a missing file needs to be
10463 kept that way if the user did it.
10467 Note that a package should <em>not</em> modify a
10468 <prgn>dpkg</prgn>-handled conffile in its maintainer
10469 scripts. Doing this will lead to <prgn>dpkg</prgn> giving
10470 the user confusing and possibly dangerous options for
10471 conffile update when the package is upgraded.</p>
10474 <sect><heading>Fully-featured maintainer script configuration
10479 For files which contain site-specific information such as
10480 the hostname and networking details and so forth, it is
10481 better to create the file in the package's
10482 <prgn>postinst</prgn> script.
10486 This will typically involve examining the state of the rest
10487 of the system to determine values and other information, and
10488 may involve prompting the user for some information which
10489 can't be obtained some other way.
10493 When using this method there are a couple of important
10494 issues which should be considered:
10498 If you discover a bug in the program which generates the
10499 configuration file, or if the format of the file changes
10500 from one version to the next, you will have to arrange for
10501 the postinst script to do something sensible - usually this
10502 will mean editing the installed configuration file to remove
10503 the problem or change the syntax. You will have to do this
10504 very carefully, since the user may have changed the file,
10505 perhaps to fix the very problem that your script is trying
10506 to deal with - you will have to detect these situations and
10507 deal with them correctly.
10511 If you do go down this route it's probably a good idea to
10512 make the program that generates the configuration file(s) a
10513 separate program in <file>/usr/sbin</file>, by convention called
10514 <file><var>package</var>config</file> and then run that if
10515 appropriate from the post-installation script. The
10516 <tt><var>package</var>config</tt> program should not
10517 unquestioningly overwrite an existing configuration - if its
10518 mode of operation is geared towards setting up a package for
10519 the first time (rather than any arbitrary reconfiguration
10520 later) you should have it check whether the configuration
10521 already exists, and require a <tt>--force</tt> flag to
10522 overwrite it.</p></sect>
10525 <appendix id="pkg-alternatives"><heading>Alternative versions of
10526 an interface - <prgn>update-alternatives</prgn> (from old
10531 When several packages all provide different versions of the
10532 same program or file it is useful to have the system select a
10533 default, but to allow the system administrator to change it
10534 and have their decisions respected.
10538 For example, there are several versions of the <prgn>vi</prgn>
10539 editor, and there is no reason to prevent all of them from
10540 being installed at once, each under their own name
10541 (<prgn>nvi</prgn>, <prgn>vim</prgn> or whatever).
10542 Nevertheless it is desirable to have the name <tt>vi</tt>
10543 refer to something, at least by default.
10547 If all the packages involved cooperate, this can be done with
10548 <prgn>update-alternatives</prgn>.
10552 Each package provides its own version under its own name, and
10553 calls <prgn>update-alternatives</prgn> in its postinst to
10554 register its version (and again in its prerm to deregister
10559 See the man page <manref name="update-alternatives"
10560 section="8"> for details.
10564 If <prgn>update-alternatives</prgn> does not seem appropriate
10565 you may wish to consider using diversions instead.</p>
10568 <appendix id="pkg-diversions"><heading>Diversions - overriding a
10569 package's version of a file (from old Packaging Manual)
10573 It is possible to have <prgn>dpkg</prgn> not overwrite a file
10574 when it reinstalls the package it belongs to, and to have it
10575 put the file from the package somewhere else instead.
10579 This can be used locally to override a package's version of a
10580 file, or by one package to override another's version (or
10581 provide a wrapper for it).
10585 Before deciding to use a diversion, read <ref
10586 id="pkg-alternatives"> to see if you really want a diversion
10587 rather than several alternative versions of a program.
10591 There is a diversion list, which is read by <prgn>dpkg</prgn>,
10592 and updated by a special program <prgn>dpkg-divert</prgn>.
10593 Please see <manref name="dpkg-divert" section="8"> for full
10594 details of its operation.
10598 When a package wishes to divert a file from another, it should
10599 call <prgn>dpkg-divert</prgn> in its preinst to add the
10600 diversion and rename the existing file. For example,
10601 supposing that a <prgn>smailwrapper</prgn> package wishes to
10602 install a wrapper around <file>/usr/sbin/smail</file>:
10604 dpkg-divert --package smailwrapper --add --rename \
10605 --divert /usr/sbin/smail.real /usr/sbin/smail
10606 </example> The <tt>--package smailwrapper</tt> ensures that
10607 <prgn>smailwrapper</prgn>'s copy of <file>/usr/sbin/smail</file>
10608 can bypass the diversion and get installed as the true version.
10609 It's safe to add the diversion unconditionally on upgrades since
10610 it will be left unchanged if it already exists, but
10611 <prgn>dpkg-divert</prgn> will display a message. To suppress that
10612 message, make the command conditional on the version from which
10613 the package is being upgraded:
10615 if [ upgrade != "$1" ] || dpkg --compare-versions "$2" lt 1.0-2; then
10616 dpkg-divert --package smailwrapper --add --rename \
10617 --divert /usr/sbin/smail.real /usr/sbin/smail
10619 </example> where <tt>1.0-2</tt> is the version at which the
10620 diversion was first added to the package. Running the command
10621 during abort-upgrade is pointless but harmless.
10625 The postrm has to do the reverse:
10627 if [ remove = "$1" -o abort-install = "$1" -o disappear = "$1" ]; then
10628 dpkg-divert --package smailwrapper --remove --rename \
10629 --divert /usr/sbin/smail.real /usr/sbin/smail
10631 </example> If the diversion was added at a particular version, the
10632 postrm should also handle the failure case of upgrading from an
10633 older version (unless the older version is so old that direct
10634 upgrades are no longer supported):
10636 if [ abort-upgrade = "$1" ] && dpkg --compare-versions "$2" lt 1.0-2; then
10637 dpkg-divert --package smailwrapper --remove --rename \
10638 --divert /usr/sbin/smail.real /usr/sbin/smail
10640 </example> where <tt>1.02-2</tt> is the version at which the
10641 diversion was first added to the package. The postrm should not
10642 remove the diversion on upgrades both because there's no reason to
10643 remove the diversion only to immediately re-add it and since the
10644 postrm of the old package is run after unpacking so the removal of
10645 the diversion will fail.
10649 Do not attempt to divert a file which is vitally important for
10650 the system's operation - when using <prgn>dpkg-divert</prgn>
10651 there is a time, after it has been diverted but before
10652 <prgn>dpkg</prgn> has installed the new version, when the file
10653 does not exist.</p>
10658 <!-- Local variables: -->
10659 <!-- indent-tabs-mode: t -->
10661 <!-- vim:set ai et sts=2 sw=2 tw=76: -->