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 59 Temple Place - Suite 330, Boston, MA 02111-1307, 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>debian-policy</package>.
164 The current version of this document is also available from
165 the Debian web mirrors at
166 <tt><url name="/doc/debian-policy/"
167 id="http://www.debian.org/doc/debian-policy/"></tt>
168 and from the Debian archive mirrors at
169 <tt><url name="/doc/package-developer/policy.txt.gz"
170 id="http://ftp.debian.org/debian/doc/package-developer/policy.txt.gz"></tt>.
171 Also available from the same directory are several other
172 formats: <file>policy.html.tar.gz</file>, <file>policy.pdf.gz</file>
173 and <file>policy.ps.gz</file>.
177 The <package>debian-policy</package> package also includes the file
178 <file>upgrading-checklist.txt</file> which indicates policy
179 changes between versions of this document.
184 <heading>Authors and Maintainers</heading>
187 Originally called "Debian GNU/Linux Policy Manual", this
188 manual was initially written in 1996 by Ian Jackson.
189 It was revised on November 27th, 1996 by David A. Morris.
190 Christian Schwarz added new sections on March 15th, 1997,
191 and reworked/restructured it in April-July 1997.
192 Christoph Lameter contributed the "Web Standard".
193 Julian Gilbey largely restructured it in 2001.
197 Since September 1998, the responsibility for the contents of
198 this document lies on the <url name="debian-policy mailing list"
199 id="mailto:debian-policy@lists.debian.org">. Proposals
200 are discussed there and inserted into policy after a certain
201 consensus is established.
202 <!-- insert shameless policy-process plug here eventually -->
203 The actual editing is done by a group of maintainers that have
204 no editorial powers. These are the current maintainers:
207 <item>Julian Gilbey</item>
208 <item>Branden Robinson</item>
209 <item>Josip Rodin</item>
210 <item>Manoj Srivastava</item>
215 While the authors of this document have tried hard to avoid
216 typos and other errors, these do still occur. If you discover
217 an error in this manual or if you want to give any
218 comments, suggestions, or criticisms please send an email to
219 the Debian Policy List,
220 <email>debian-policy@lists.debian.org</email>, or submit a
221 bug report against the <tt>debian-policy</tt> package.
225 Please do not try to reach the individual authors or maintainers
226 of the Policy Manual regarding changes to the Policy.
231 <heading>Related documents</heading>
234 There are several other documents other than this Policy Manual
235 that are necessary to fully understand some Debian policies and
240 The external "sub-policy" documents are referred to in:
241 <list compact="compact">
242 <item><ref id="fhs"></item>
243 <item><ref id="virtual_pkg"></item>
244 <item><ref id="menus"></item>
245 <item><ref id="mime"></item>
246 <item><ref id="perl"></item>
247 <item><ref id="maintscriptprompt"></item>
248 <item><ref id="emacs"></item>
253 In addition to those, which carry the weight of policy, there
254 is the Debian Developer's Reference. This document describes
255 procedures and resources for Debian developers, but it is
256 <em>not</em> normative; rather, it includes things that don't
257 belong into the Policy, such as best practices for developers.
261 The Developer's Reference is available in the
262 <package>developers-reference</package> package.
263 It's also available from the Debian web mirrors at
264 <tt><url name="/doc/developers-reference/"
265 id="http://www.debian.org/doc/developers-reference/"></tt>.
273 <heading>The Debian Archive</heading>
276 The Debian GNU/Linux system is maintained and distributed as a
277 collection of <em>packages</em>. Since there are so many of
278 them (currently well over 6000), they are split into
279 <em>sections</em> and given <em>priorities</em> to simplify
280 the handling of them.
284 The effort of the Debian project is to build a free operating
285 system, but not every package we want to make accessible is
286 <em>free</em> in our sense (see the Debian Free Software
287 Guidelines, below), or may be imported/exported without
288 restrictions. Thus, the archive is split into the sections
289 based on their licenses and other restrictions.
293 The aims of this are:
295 <list compact="compact">
296 <item>to allow us to make as much software available as we can</item>
297 <item>to allow us to encourage everyone to write free software,
299 <item>to allow us to make it easy for people to produce
300 CD-ROMs of our system without violating any licenses,
301 import/export restrictions, or any other laws.</item>
306 The <em>main</em> and the <em>non-US/main</em> sections
307 together form the <em>Debian GNU/Linux distribution</em>.
311 Packages in the other sections are not considered to be part
312 of the Debian distribution, although we support their use and
313 provide infrastructure for them (such as our bug-tracking
314 system and mailing lists). This Debian Policy Manual applies
315 to these packages as well.
319 <heading>The Debian Free Software Guidelines</heading>
321 The Debian Free Software Guidelines (DFSG) form our
322 definition of "free software". These are:
324 <tag>Free Redistribution
327 The license of a Debian component may not restrict any
328 party from selling or giving away the software as a
329 component of an aggregate software distribution
330 containing programs from several different
331 sources. The license may not require a royalty or
332 other fee for such sale.
337 The program must include source code, and must allow
338 distribution in source code as well as compiled form.
343 The license must allow modifications and derived
344 works, and must allow them to be distributed under the
345 same terms as the license of the original software.
347 <tag>Integrity of The Author's Source Code
350 The license may restrict source-code from being
351 distributed in modified form <em>only</em> if the
352 license allows the distribution of "patch files"
353 with the source code for the purpose of modifying the
354 program at build time. The license must explicitly
355 permit distribution of software built from modified
356 source code. The license may require derived works to
357 carry a different name or version number from the
358 original software. (This is a compromise. The Debian
359 Project encourages all authors to not restrict any
360 files, source or binary, from being modified.)
362 <tag>No Discrimination Against Persons or Groups
365 The license must not discriminate against any person
368 <tag>No Discrimination Against Fields of Endeavor
371 The license must not restrict anyone from making use
372 of the program in a specific field of endeavor. For
373 example, it may not restrict the program from being
374 used in a business, or from being used for genetic
377 <tag>Distribution of License
380 The rights attached to the program must apply to all
381 to whom the program is redistributed without the need
382 for execution of an additional license by those
385 <tag>License Must Not Be Specific to Debian
388 The rights attached to the program must not depend on
389 the program's being part of a Debian system. If the
390 program is extracted from Debian and used or
391 distributed without Debian but otherwise within the
392 terms of the program's license, all parties to whom
393 the program is redistributed must have the same
394 rights as those that are granted in conjunction with
397 <tag>License Must Not Contaminate Other Software
400 The license must not place restrictions on other
401 software that is distributed along with the licensed
402 software. For example, the license must not insist
403 that all other programs distributed on the same medium
404 must be free software.
406 <tag>Example Licenses
409 The "GPL," "BSD," and "Artistic" licenses are examples of
410 licenses that we consider <em>free</em>.
417 <heading>Sections</heading>
420 <heading>The main section</heading>
423 Every package in <em>main</em> and <em>non-US/main</em>
424 must comply with the DFSG (Debian Free Software
429 In addition, the packages in <em>main</em>
430 <list compact="compact">
432 must not require a package outside of <em>main</em>
433 for compilation or execution (thus, the package must
434 not declare a "Depends", "Recommends", or
435 "Build-Depends" relationship on a non-<em>main</em>
439 must not be so buggy that we refuse to support them,
443 must meet all policy requirements presented in this
450 Similarly, the packages in <em>non-US/main</em>
451 <list compact="compact">
453 must not require a package outside of <em>main</em>
454 or <em>non-US/main</em> for compilation or
458 must not be so buggy that we refuse to support them,
461 must meet all policy requirements presented in this
470 <heading>The contrib section</heading>
473 Every package in <em>contrib</em> and
474 <em>non-US/contrib</em> must comply with the DFSG.
478 In addition, the packages in <em>contrib</em> and
479 <em>non-US/contrib</em>
480 <list compact="compact">
482 must not be so buggy that we refuse to support them,
486 must meet all policy requirements presented in this
493 Furthermore, packages in <em>contrib</em> must not require
494 a package in a <em>non-US</em> section for compilation or
499 Examples of packages which would be included in
500 <em>contrib</em> or <em>non-US/contrib</em> are:
501 <list compact="compact">
503 free packages which require <em>contrib</em>,
504 <em>non-free</em> packages or packages which are not
505 in our archive at all for compilation or execution,
509 wrapper packages or other sorts of free accessories for
516 <sect1 id="non-free">
517 <heading>The non-free section</heading>
520 Packages must be placed in <em>non-free</em> or
521 <em>non-US/non-free</em> if they are not compliant with
522 the DFSG or are encumbered by patents or other legal
523 issues that make their distribution problematic.
527 In addition, the packages in <em>non-free</em> and
528 <em>non-US/non-free</em>
529 <list compact="compact">
531 must not be so buggy that we refuse to support them,
535 must meet all policy requirements presented in this
536 manual that it is possible for them to meet.
538 It is possible that there are policy
539 requirements which the package is unable to
540 meet, for example, if the source is
541 unavailable. These situations will need to be
542 handled on a case-by-case basis.
550 <heading>The non-US sections</heading>
553 Non-free programs with cryptographic program code need to
554 be stored on the <em>non-us</em> server because of export
555 restrictions of the U.S.
559 Programs which use patented algorithms that have a
560 restricted license also need to be stored on "non-us",
561 since that is located in a country where it is not allowed
562 to patent algorithms.
566 A package depends on another package which is distributed
567 via the non-us server has to be stored on the non-us
573 <sect id="pkgcopyright">
574 <heading>Copyright considerations</heading>
577 Every package must be accompanied by a verbatim copy of
578 its copyright and distribution license in the file
579 <file>/usr/share/doc/<var>package</var>/copyright</file>
580 (see <ref id="copyrightfile"> for further details).
584 We reserve the right to restrict files from being included
585 anywhere in our archives if
586 <list compact="compact">
588 their use or distribution would break a law,
591 there is an ethical conflict in their distribution or
595 we would have to sign a license for them, or
598 their distribution would conflict with other project
605 Programs whose authors encourage the user to make
606 donations are fine for the main distribution, provided
607 that the authors do not claim that not donating is
608 immoral, unethical, illegal or something similar; in such
609 a case they must go in <em>non-free</em>.
613 Packages whose copyright permission notices (or patent
614 problems) do not even allow redistribution of binaries
615 only, and where no special permission has been obtained,
616 must not be placed on the Debian FTP site and its mirrors
621 Note that under international copyright law (this applies
622 in the United States, too), <em>no</em> distribution or
623 modification of a work is allowed without an explicit
624 notice saying so. Therefore a program without a copyright
625 notice <em>is</em> copyrighted and you may not do anything
626 to it without risking being sued! Likewise if a program
627 has a copyright notice but no statement saying what is
628 permitted then nothing is permitted.
632 Many authors are unaware of the problems that restrictive
633 copyrights (or lack of copyright notices) can cause for
634 the users of their supposedly-free software. It is often
635 worthwhile contacting such authors diplomatically to ask
636 them to modify their license terms. However, this can be a
637 politically difficult thing to do and you should ask for
638 advice on the <tt>debian-legal</tt> mailing list first, as
643 When in doubt about a copyright, send mail to
644 <email>debian-legal@lists.debian.org</email>. Be prepared
645 to provide us with the copyright statement. Software
646 covered by the GPL, public domain software and BSD-like
647 copyrights are safe; be wary of the phrases "commercial
648 use prohibited" and "distribution restricted".
652 <sect id="subsections">
653 <heading>Subsections</heading>
656 The packages in the sections <em>main</em>,
657 <em>contrib</em> and <em>non-free</em> are grouped further
658 into <em>subsections</em> to simplify handling.
662 The section and subsection for each package should be
663 specified in the package's <tt>Section</tt> control
664 record (see <ref id="f-Section">).
665 However, the maintainer of the Debian archive
666 may override this selection to ensure the consistency of
667 the Debian distribution. The <tt>Section</tt> field
668 should be of the form:
669 <list compact="compact">
671 <em>subsection</em> if the package is in the
672 <em>main</em> section,
675 <em>section/subsection</em> if the package is in
676 the <em>contrib</em> or <em>non-free</em> section,
680 <tt>non-US</tt>, <tt>non-US/contrib</tt> or
681 <tt>non-US/non-free</tt> if the package is in
682 <em>non-US/main</em>, <em>non-US/contrib</em> or
683 <em>non-US/non-free</em> respectively.
689 The Debian archive maintainers provide the authoritative
690 list of subsections. At present, they are:
691 <em>admin</em>, <em>base</em>, <em>comm</em>,
692 <em>contrib</em>, <em>devel</em>, <em>doc</em>,
693 <em>editors</em>, <em>electronics</em>, <em>embedded</em>,
694 <em>games</em>, <em>gnome</em> <em>graphics</em>,
695 <em>hamradio</em>, <em>interpreters</em>, <em>kde</em>,
696 <em>libs</em>, <em>libdevel</em>, <em>mail</em>,
697 <em>math</em>, <em>misc</em>, <em>net</em>, <em>news</em>,
698 <em>non-US</em>, <em>non-free</em>, <em>oldlibs</em>,
699 <em>otherosfs</em>, <em>perl</em>, <em>python</em>
700 <em>science</em>, <em>shells</em>,
701 <em>sound</em>, <em>tex</em>, <em>text</em>,
702 <em>utils</em>, <em>web</em>, <em>x11</em>.
706 <sect id="priorities">
707 <heading>Priorities</heading>
710 Each package should have a <em>priority</em> value, which is
711 included in the package's <em>control record</em>
712 (see <ref id="f-Priority">).
713 This information is used by the Debian package management tools to
714 separate high-priority packages from less-important packages.
718 The following <em>priority levels</em> are recognised by the
719 Debian package management tools.
721 <tag><tt>required</tt></tag>
723 Packages which are necessary for the proper
724 functioning of the system. You must not remove these
725 packages or your system may become totally broken and
726 you may not even be able to use <prgn>dpkg</prgn> to
727 put things back. Systems with only the
728 <tt>required</tt> packages are probably unusable, but
729 they do have enough functionality to allow the
730 sysadmin to boot and install more software.
732 <tag><tt>important</tt></tag>
734 Important programs, including those which one would
735 expect to find on any Unix-like system. If the
736 expectation is that an experienced Unix person who
737 found it missing would say "What on earth is going on,
738 where is <prgn>foo</prgn>?", it must be an
739 <tt>important</tt> package.<footnote>
740 This is an important criterion because we are
741 trying to produce, amongst other things, a free
744 Other packages without which the system will not run
745 well or be usable must also have priority
746 <tt>important</tt>. This does
747 <em>not</em> include Emacs, the X Window System, TeX
748 or any other large applications. The
749 <tt>important</tt> packages are just a bare minimum of
750 commonly-expected and necessary tools.
752 <tag><tt>standard</tt></tag>
754 These packages provide a reasonably small but not too
755 limited character-mode system. This is what will be
756 installed by default if the user doesn't select anything
757 else. It doesn't include many large applications.
759 <tag><tt>optional</tt></tag>
761 (In a sense everything that isn't required is
762 optional, but that's not what is meant here.) This is
763 all the software that you might reasonably want to
764 install if you didn't know what it was and don't have
765 specialized requirements. This is a much larger system
766 and includes the X Window System, a full TeX
767 distribution, and many applications. Note that
768 optional packages should not conflict with each other.
770 <tag><tt>extra</tt></tag>
772 This contains all packages that conflict with others
773 with required, important, standard or optional
774 priorities, or are only likely to be useful if you
775 already know what they are or have specialised
782 Packages must not depend on packages with lower priority
783 values (excluding build-time dependencies). In order to
784 ensure this, the priorities of one or more packages may need
793 <heading>Binary packages</heading>
796 The Debian GNU/Linux distribution is based on the Debian
797 package management system, called <prgn>dpkg</prgn>. Thus,
798 all packages in the Debian distribution must be provided
799 in the <tt>.deb</tt> file format.
803 <heading>The package name</heading>
806 Every package must have a name that's unique within the Debian
811 The package name is included in the control field
812 <tt>Package</tt>, the format of which is described
813 in <ref id="f-Package">.
814 The package name is also included as a part of the file name
815 of the <tt>.deb</tt> file.
820 <heading>The version of a package</heading>
823 Every package has a version number recorded in its
824 <tt>Version</tt> control file field, described in
825 <ref id="f-Version">.
829 The package management system imposes an ordering on version
830 numbers, so that it can tell whether packages are being up- or
831 downgraded and so that package system front end applications
832 can tell whether a package it finds available is newer than
833 the one installed on the system. The version number format
834 has the most significant parts (as far as comparison is
835 concerned) at the beginning.
839 If an upstream package has problematic version numbers they
840 should be converted to a sane form for use in the
841 <tt>Version</tt> field.
845 <heading>Version numbers based on dates</heading>
848 In general, Debian packages should use the same version
849 numbers as the upstream sources.
853 However, in some cases where the upstream version number is
854 based on a date (e.g., a development "snapshot" release) the
855 package management system cannot handle these version
856 numbers without epochs. For example, dpkg will consider
857 "96May01" to be greater than "96Dec24".
861 To prevent having to use epochs for every new upstream
862 version, the version number should be changed to the
863 following format in such cases: "19960501", "19961224". It
864 is up to the maintainer whether he/she wants to bother the
865 upstream maintainer to change the version numbers upstream,
870 Note that other version formats based on dates which are
871 parsed correctly by the package management system should
872 <em>not</em> be changed.
876 Native Debian packages (i.e., packages which have been
877 written especially for Debian) whose version numbers include
878 dates should always use the "YYYYMMDD" format.
885 <heading>The maintainer of a package</heading>
888 Every package must have a Debian maintainer (the
889 maintainer may be one person or a group of people
890 reachable from a common email address, such as a mailing
891 list). The maintainer is responsible for ensuring that
892 the package is placed in the appropriate distributions.
896 The maintainer must be specified in the
897 <tt>Maintainer</tt> control field with their correct name
898 and a working email address. If one person maintains
899 several packages, he/she should try to avoid having
900 different forms of their name and email address in
901 the <tt>Maintainer</tt> fields of those packages.
905 The format of the <tt>Maintainer</tt> control field is
906 described in <ref id="f-Maintainer">.
910 If the maintainer of a package quits from the Debian
911 project, "Debian QA Group"
912 <email>packages@qa.debian.org</email> takes over the
913 maintainership of the package until someone else
914 volunteers for that task. These packages are called
915 <em>orphaned packages</em>.<footnote>
916 The detailed procedure for doing this gracefully can
917 be found in the Debian Developer's Reference,
918 see <ref id="related">.
923 <sect id="descriptions">
924 <heading>The description of a package</heading>
927 Every Debian package must have an extended description
928 stored in the appropriate field of the control record.
929 The technical information about the format of the
930 <tt>Description</tt> field is in <ref id="f-Description">.
934 The description should describe the package (the program) to a
935 user (system administrator) who has never met it before so that
936 they have enough information to decide whether they want to
937 install it. This description should not just be copied verbatim
938 from the program's documentation.
942 Put important information first, both in the synopsis and
943 extended description. Sometimes only the first part of the
944 synopsis or of the description will be displayed. You can
945 assume that there will usually be a way to see the whole
946 extended description.
950 The description should also give information about the
951 significant dependencies and conflicts between this package
952 and others, so that the user knows why these dependencies and
953 conflicts have been declared.
957 Instructions for configuring or using the package should
958 not be included (that is what installation scripts,
959 manual pages, info files, etc., are for). Copyright
960 statements and other administrivia should not be included
961 either (that is what the copyright file is for).
964 <sect1 id="synopsis"><heading>The single line synopsis</heading>
967 The single line synopsis should be kept brief - certainly
972 Do not include the package name in the synopsis line. The
973 display software knows how to display this already, and you
974 do not need to state it. Remember that in many situations
975 the user may only see the synopsis line - make it as
976 informative as you can.
981 <sect1 id="extendeddesc"><heading>The extended description</heading>
984 Do not try to continue the single line synopsis into the
985 extended description. This will not work correctly when
986 the full description is displayed, and makes no sense
987 where only the summary (the single line synopsis) is
992 The extended description should describe what the package
993 does and how it relates to the rest of the system (in terms
994 of, for example, which subsystem it is which part of).
998 The description field needs to make sense to anyone, even
999 people who have no idea about any of the things the
1000 package deals with.<footnote>
1001 The blurb that comes with a program in its
1002 announcements and/or <prgn>README</prgn> files is
1003 rarely suitable for use in a description. It is
1004 usually aimed at people who are already in the
1005 community where the package is used.
1014 <heading>Dependencies</heading>
1017 Every package must specify the dependency information
1018 about other packages that are required for the first to
1023 For example, a dependency entry must be provided for any
1024 shared libraries required by a dynamically-linked executable
1025 binary in a package.
1029 Packages are not required to declare any dependencies they
1030 have on other packages which are marked <tt>Essential</tt>
1031 (see below), and should not do so unless they depend on a
1032 particular version of that package.
1036 Sometimes, a package requires another package to be installed
1037 <em>and</em> configured before it can be installed. In this
1038 case, you must specify a <tt>Pre-Depends</tt> entry for
1043 You should not specify a <tt>Pre-Depends</tt> entry for a
1044 package before this has been discussed on the
1045 <tt>debian-devel</tt> mailing list and a consensus about
1046 doing that has been reached.
1050 The format of the package interrelationship control fields is
1051 described in <ref id="relationships">.
1055 <sect id="virtual_pkg">
1056 <heading>Virtual packages</heading>
1059 Sometimes, there are several packages which offer
1060 more-or-less the same functionality. In this case, it's
1061 useful to define a <em>virtual package</em> whose name
1062 describes that common functionality. (The virtual
1063 packages only exist logically, not physically; that's why
1064 they are called <em>virtual</em>.) The packages with this
1065 particular function will then <em>provide</em> the virtual
1066 package. Thus, any other package requiring that function
1067 can simply depend on the virtual package without having to
1068 specify all possible packages individually.
1072 All packages should use virtual package names where
1073 appropriate, and arrange to create new ones if necessary.
1074 They should not use virtual package names (except privately,
1075 amongst a cooperating group of packages) unless they have
1076 been agreed upon and appear in the list of virtual package
1077 names. (See also <ref id="virtual">)
1081 The latest version of the authoritative list of virtual
1082 package names can be found in the <tt>debian-policy</tt> package.
1083 It is also available from the Debian web mirrors at
1084 <tt><url name="/doc/packaging-manuals/virtual-package-names-list.txt"
1085 id="http://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt"></tt>
1086 and from the Debian archive mirrors at
1087 <tt><url name="/doc/package-developer/virtual-package-names-list.txt"
1088 id="http://ftp.debian.org/debian/doc/package-developer/virtual-package-names-list.txt"></tt>.
1092 The procedure for updating the list is described in the preface
1099 <heading>Base system</heading>
1102 The <tt>base system</tt> is a minimum subset of the Debian
1103 GNU/Linux system that is installed before everything else
1104 on a new system. Thus, only very few packages are allowed
1105 to go into the <tt>base</tt> section to keep the required
1106 disk usage very small.
1110 Most of these packages will have the priority value
1111 <tt>required</tt> or at least <tt>important</tt>, and many
1112 of them will be tagged <tt>essential</tt> (see below).
1117 <heading>Essential packages</heading>
1120 Some packages are tagged <tt>essential</tt> for a system
1121 using the <tt>Essential</tt> control file field.
1122 The format of the <tt>Essential</tt> control field is
1123 described in <ref id="f-Essential">.
1127 Since these packages cannot be easily removed (one has to
1128 specify an extra <em>force option</em> to
1129 <prgn>dpkg</prgn> to do so), this flag must not be used
1130 unless absolutely necessary. A shared library package
1131 must not be tagged <tt>essential</tt>; dependencies will
1132 prevent its premature removal, and we need to be able to
1133 remove it when it has been superseded.
1137 Since dpkg will not prevent upgrading of other packages
1138 while an <tt>essential</tt> package is in an unconfigured
1139 state, all <tt>essential</tt> packages must supply all of
1140 their core functionality even when unconfigured. If the
1141 package cannot satisfy this requirement it must not be
1142 tagged as essential, and any packages depending on this
1143 package must instead have explicit dependency fields as
1148 You must not tag any packages <tt>essential</tt> before
1149 this has been discussed on the <tt>debian-devel</tt>
1150 mailing list and a consensus about doing that has been
1156 <heading>Tasks</heading>
1159 The Debian install process allows the user to choose from
1160 a number of common tasks which a Debian system can be used to
1161 perform. Selecting a task with <prgn>tasksel</prgn> causes
1162 a set of packages that are useful in performing that task to be
1167 This set of packages is all available packages which have the
1168 name of the selected task in the <tt>Task</tt> field of their
1169 control file. The format of this field is a list of tasks,
1170 separated by commas.
1174 You should not tag any packages as belonging to a task
1175 before this has been discussed on the
1176 <em>debian-devel</em> mailing list and a consensus about
1177 doing that has been reached.
1181 For third parties (and historical reasons), tasksel also
1182 supports constructing tasks based on <em>task
1183 packages</em>. These are packages whose names begin with
1184 <em>task-</em>. Task packages should not be included in the
1189 <sect id="maintscripts">
1190 <heading>Maintainer Scripts</heading>
1193 The package installation scripts should avoid producing
1194 output which it is unnecessary for the user to see and
1195 should rely on <prgn>dpkg</prgn> to stave off boredom on
1196 the part of a user installing many packages. This means,
1197 amongst other things, using the <tt>--quiet</tt> option on
1198 <prgn>install-info</prgn>.
1202 Errors which occur during the execution of an installation
1203 script must be checked and the installation must not
1204 continue after an error.
1208 Note that in general <ref id="scripts"> applies to package
1209 maintainer scripts, too.
1213 You should not use <prgn>dpkg-divert</prgn> on a file
1214 belonging to another package without consulting the
1215 maintainer of that package first.
1219 All packages which supply an instance of a common command
1220 name (or, in general, filename) should generally use
1221 <prgn>update-alternatives</prgn>, so that they may be
1222 installed together. If <prgn>update-alternatives</prgn>
1223 is not used, then each package must use
1224 <tt>Conflicts</tt> to ensure that other packages are
1225 de-installed. (In this case, it may be appropriate to
1226 specify a conflict against earlier versions of something
1227 that previously did not use
1228 <prgn>update-alternatives</prgn>; this is an exception to
1229 the usual rule that versioned conflicts should be
1233 <sect1 id="maintscriptprompt">
1234 <heading>Prompting in maintainer scripts</heading>
1236 Package maintainer scripts may prompt the user if
1237 necessary. Prompting should be done by communicating
1238 through a program, such as <prgn>debconf</prgn>, which
1239 conforms to the Debian Configuration management
1240 specification, version 2 or higher. Prompting the user by
1241 other means, such as by hand<footnote>
1242 From the Jargon file: by hand 2. By extension,
1243 writing code which does something in an explicit or
1244 low-level way for which a presupplied library
1245 (<em>debconf, in this instance</em>) routine ought
1246 to have been available.
1247 </footnote>, is now deprecated.
1251 The Debian Configuration management specification is included
1252 in the <file>debconf_specification</file> files in the
1253 <package>debian-policy</package> package.
1254 It is also available from the Debian web mirrors at
1255 <tt><url name="/doc/packaging-manuals/debconf_specification.html"
1256 id="http://www.debian.org/doc/packaging-manuals/debconf_specification.html"></tt>
1257 and from the Debian archive mirrors at
1258 <tt><url name="/doc/package-developer/debconf_specification.txt.gz"
1259 id="http://ftp.debian.org/debian/doc/package-developer/debconf_specification.txt.gz"></tt>.
1263 Packages which use the Debian Configuration management
1264 specification may contain an additional
1265 <prgn>config</prgn> script and a <tt>templates</tt>
1266 file in their control archive<footnote>
1267 The control.tar.gz inside the .deb.
1268 See <manref name="deb" section="5">.
1270 The <prgn>config</prgn> script might be run before the
1271 <prgn>preinst</prgn> script, and before the package is unpacked
1272 or any of its dependencies or pre-dependancies are satisfied.
1273 Therefore it must work using only the tools present in
1274 <em>essential</em> packages.<footnote>
1275 <package>Debconf</package> or another tool that
1276 implements the Debian Configuration management
1277 specification will also be installed, and any
1278 versioned dependencies on it will be satisfied
1279 before preconfiguration begins.
1284 Packages should try to minimize the amount of prompting
1285 they need to do, and they should ensure that the user
1286 will only ever be asked each question once. This means
1287 that packages should try to use appropriate shared
1288 configuration files (such as <file>/etc/papersize</file> and
1289 <file>/etc/news/server</file>), and shared
1290 <package>debconf</package> variables rather than each
1291 prompting for their own list of required pieces of
1296 It also means that an upgrade should not ask the same
1297 questions again, unless the user has used
1298 <tt>dpkg --purge</tt> to remove the package's configuration.
1299 The answers to configuration questions should be stored in an
1300 appropriate place in <file>/etc</file> so that the user can
1301 modify them, and how this has been done should be
1306 If a package has a vitally important piece of
1307 information to pass to the user (such as "don't run me
1308 as I am, you must edit the following configuration files
1309 first or you risk your system emitting badly-formatted
1310 messages"), it should display this in the
1311 <prgn>config</prgn> or <prgn>postinst</prgn> script and
1312 prompt the user to hit return to acknowledge the
1313 message. Copyright messages do not count as vitally
1314 important (they belong in
1315 <file>/usr/share/doc/<var>package</var>/copyright</file>);
1316 neither do instructions on how to use a program (these
1317 should be in on-line documentation, where all the users
1322 Any necessary prompting should almost always be confined
1323 to the <prgn>config</prgn> or <prgn>postinst</prgn>
1324 script. If it is done in the <prgn>postinst</prgn>, it
1325 should be protected with a conditional so that
1326 unnecessary prompting doesn't happen if a package's
1327 installation fails and the <prgn>postinst</prgn> is
1328 called with <tt>abort-upgrade</tt>,
1329 <tt>abort-remove</tt> or <tt>abort-deconfigure</tt>.
1339 <heading>Source packages</heading>
1341 <sect id="standardsversion">
1342 <heading>Standards conformance</heading>
1345 Source packages should specify the most recent version number
1346 of this policy document with which your package complied
1347 when it was last updated.
1351 This information may be used to file bug reports
1352 automatically if your package becomes too much out of date.
1356 The version is specified in the <tt>Standards-Version</tt>
1358 The format of the <tt>Standards-Version</tt> field is
1359 described in <ref id="f-Standards-Version">.
1363 You should regularly, and especially if your package has
1364 become out of date, check for the newest Policy Manual
1365 available and update your package, if necessary. When your
1366 package complies with the new standards you should update the
1367 <tt>Standards-Version</tt> source package field and
1368 release it.<footnote>
1369 See the file <file>upgrading-checklist</file> for
1370 information about policy which has changed between
1371 different versions of this document.
1377 <sect id="pkg-relations">
1378 <heading>Package relationships</heading>
1381 Source packages should specify which binary packages they
1382 require to be installed or not to be installed in order to
1383 build correctly. For example, if building a package
1384 requires a certain compiler, then the compiler should be
1385 specified as a build-time dependency.
1389 It is not necessary to explicitly specify build-time
1390 relationships on a minimal set of packages that are always
1391 needed to compile, link and put in a Debian package a
1392 standard "Hello World!" program written in C or C++. The
1393 required packages are called <em>build-essential</em>, and
1394 an informational list can be found in
1395 <file>/usr/share/doc/build-essential/list</file> (which is
1396 contained in the <tt>build-essential</tt>
1399 <list compact="compact">
1401 This allows maintaining the list separately
1402 from the policy documents (the list does not
1403 need the kind of control that the policy
1407 Having a separate package allows one to install
1408 the build-essential packages on a machine, as
1409 well as allowing other packages such as tasks to
1410 require installation of the build-essential
1411 packages using the depends relation.
1414 The separate package allows bug reports against
1415 the list to be categorized separately from
1416 the policy management process in the BTS.
1423 When specifying the set of build-time dependencies, one
1424 should list only those packages explicitly required by the
1425 build. It is not necessary to list packages which are
1426 required merely because some other package in the list of
1427 build-time dependencies depends on them.<footnote>
1428 The reason for this is that dependencies change, and
1429 you should list all those packages, and <em>only</em>
1430 those packages that <em>you</em> need directly. What
1431 others need is their business. For example, if you
1432 only link against <file>libimlib</file>, you will need to
1433 build-depend on <package>libimlib2-dev</package> but
1434 not against any <tt>libjpeg*</tt> packages, even
1435 though <tt>libimlib2-dev</tt> currently depends on
1436 them: installation of <package>libimlib2-dev</package>
1437 will automatically ensure that all of its run-time
1438 dependencies are satisfied.
1443 If build-time dependencies are specified, it must be
1444 possible to build the package and produce working binaries
1445 on a system with only essential and build-essential
1446 packages installed and also those required to satisfy the
1447 build-time relationships (including any implied
1448 relationships). In particular, this means that version
1449 clauses should be used rigorously in build-time
1450 relationships so that one cannot produce bad or
1451 inconsistently configured packages when the relationships
1452 are properly satisfied.
1456 <ref id="relationships"> explains the technical details.
1461 <heading>Changes to the upstream sources</heading>
1464 If changes to the source code are made that are not
1465 specific to the needs of the Debian system, they should be
1466 sent to the upstream authors in whatever form they prefer
1467 so as to be included in the upstream version of the
1472 If you need to configure the package differently for
1473 Debian or for Linux, and the upstream source doesn't
1474 provide a way to do so, you should add such configuration
1475 facilities (for example, a new <prgn>autoconf</prgn> test
1476 or <tt>#define</tt>) and send the patch to the upstream
1477 authors, with the default set to the way they originally
1478 had it. You can then easily override the default in your
1479 <file>debian/rules</file> or wherever is appropriate.
1483 You should make sure that the <prgn>configure</prgn> utility
1484 detects the correct architecture specification string
1485 (refer to <ref id="arch-spec"> for details).
1489 If you need to edit a <prgn>Makefile</prgn> where
1490 GNU-style <prgn>configure</prgn> scripts are used, you
1491 should edit the <file>.in</file> files rather than editing the
1492 <prgn>Makefile</prgn> directly. This allows the user to
1493 reconfigure the package if necessary. You should
1494 <em>not</em> configure the package and edit the generated
1495 <prgn>Makefile</prgn>! This makes it impossible for
1496 someone else to later reconfigure the package.
1501 <sect id="dpkgchangelog">
1502 <heading>Debian changelog: <file>debian/changelog</file></heading>
1505 Changes in the Debian version of the package should be
1506 briefly explained in the Debian changelog file
1507 <file>debian/changelog</file>. This includes modifications
1508 made in the Debian package compared to the upstream one
1509 as well as other changes and updates to the package.
1511 Although there is nothing stopping an author who is also
1512 the Debian maintainer from using this changelog for all
1513 their changes, it will have to be renamed if the Debian
1514 and upstream maintainers become different people. In such
1515 a case, however, it might be better to maintain the package
1516 as a non-native package.
1521 Mistakes in changelogs are usually best rectified by making
1522 a new changelog entry rather than "rewriting history" by
1523 editing old changelog entries.
1527 The format of the <file>debian/changelog</file> allows the
1528 package building tools to discover which version of the package
1529 is being built and find out other release-specific information.
1533 That format is a series of entries like this:
1535 <example compact="compact">
1536 <var>package</var> (<var>version</var>) <var>distribution(s)</var>; urgency=<var>urgency</var>
1538 [optional blank line(s), stripped]
1540 * <var>change details</var>
1541 <var>more change details</var>
1543 [blank line(s), included in output of dpkg-parsechangelog]
1545 * <var>even more change details</var>
1547 [optional blank line(s), stripped]
1549 -- <var>maintainer name</var> <<var>email address</var>><var>[two spaces]</var> <var>date</var>
1554 <var>package</var> and <var>version</var> are the source
1555 package name and version number.
1559 <var>distribution(s)</var> lists the distributions where
1560 this version should be installed when it is uploaded - it
1561 is copied to the <tt>Distribution</tt> field in the
1562 <file>.changes</file> file. See <ref id="f-Distribution">.
1566 <var>urgency</var> is the value for the <tt>Urgency</tt>
1567 field in the <file>.changes</file> file for the upload
1568 (see <ref id="f-Urgency">). It is not possible to specify
1569 an urgency containing commas; commas are used to separate
1570 <tt><var>keyword</var>=<var>value</var></tt> settings in the
1571 <prgn>dpkg</prgn> changelog format (though there is
1572 currently only one useful <var>keyword</var>,
1573 <tt>urgency</tt>).<footnote>
1574 Recognised urgency values are <tt>low</tt>,
1575 <tt>medium</tt>, <tt>high</tt> and <tt>emergency</tt>.
1576 They have an effect on how quickly a package will be
1577 considered for inclusion into the <tt>testing</tt>
1578 distribution, and give an indication of the importance
1579 of any fixes included in this upload.
1584 The change details may in fact be any series of lines
1585 starting with at least two spaces, but conventionally each
1586 change starts with an asterisk and a separating space and
1587 continuation lines are indented so as to bring them in
1588 line with the start of the text above. Blank lines may be
1589 used here to separate groups of changes, if desired.
1593 If this upload resolves bugs recorded in the Bug Tracking
1594 System (BTS), they may be automatically closed on the
1595 inclusion of this package into the Debian archive by
1596 including the string: <tt>closes: Bug#<var>nnnnn</var></tt>
1597 in the change details.<footnote>
1598 To be precise, the string should match the following
1599 Perl regular expression:
1601 /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i
1603 Then all of the bug numbers listed will be closed by the
1604 archive maintenance script (<prgn>katie</prgn>), or in
1605 the case of an NMU, marked as fixed.
1607 This information is conveyed via the <tt>Closes</tt> field
1608 in the <tt>.changes</tt> file (see <ref id="f-Closes">).
1612 The maintainer name and email address used in the changelog
1613 should be the details of the person uploading <em>this</em>
1614 version. They are <em>not</em> necessarily those of the
1615 usual package maintainer. The information here will be
1616 copied to the <tt>Changed-By</tt> field in the
1617 <tt>.changes</tt> file (see <ref id="f-Changed-By">),
1618 and then later used to send an acknowledgement when the
1619 upload has been installed.
1623 The <var>date</var> should be in RFC822 format<footnote>
1624 This is generated by the <prgn>822-date</prgn>
1626 </footnote>; it should include the time zone specified
1627 numerically, with the time zone name or abbreviation
1628 optionally present as a comment in parentheses.
1632 The first "title" line with the package name should start
1633 at the left hand margin; the "trailer" line with the
1634 maintainer and date details should be preceded by exactly
1635 one space. The maintainer details and the date must be
1636 separated by exactly two spaces.
1640 For more information on placement of the changelog files
1641 within binary packages, please see <ref id="changelogs">.
1644 <sect1><heading>Alternative changelog formats</heading>
1647 In non-experimental packages you must use a format for
1648 <file>debian/changelog</file> which is supported by the most
1649 recent released version of <prgn>dpkg</prgn>.
1653 It is possible to use a format different from the standard
1654 one by providing a changelog parser for the format you wish
1655 to use. The parser must have an API compatible with that
1656 expected by <prgn>dpkg-genchanges</prgn> and
1657 <prgn>dpkg-gencontrol</prgn>, and it must not interact with
1660 If there is general interest in the new format, you should
1661 contact the <package>dpkg</package> maintainer to have the
1662 parser script for it included in the <prgn>dpkg</prgn>
1663 package. (You will need to agree that the parser and its
1664 manpage may be distributed under the GNU GPL, just as the rest
1665 of <prgn>dpkg</prgn> is.)
1672 <heading>Error trapping in makefiles</heading>
1675 When <prgn>make</prgn> invokes a command in a makefile
1676 (including your package's upstream makefiles and
1677 <file>debian/rules</file>), it does so using <prgn>sh</prgn>. This
1678 means that <prgn>sh</prgn>'s usual bad error handling
1679 properties apply: if you include a miniature script as one
1680 of the commands in your makefile you'll find that if you
1681 don't do anything about it then errors are not detected
1682 and <prgn>make</prgn> will blithely continue after
1687 Every time you put more than one shell command (this
1688 includes using a loop) in a makefile command you
1689 must make sure that errors are trapped. For
1690 simple compound commands, such as changing directory and
1691 then running a program, using <tt>&&</tt> rather
1692 than semicolon as a command separator is sufficient. For
1693 more complex commands including most loops and
1694 conditionals you should include a separate <tt>set -e</tt>
1695 command at the start of every makefile command that's
1696 actually one of these miniature shell scripts.
1700 <sect id="timestamps">
1701 <heading>Time Stamps</heading>
1703 Maintainers should preserve the modification times of the
1704 upstream source files in a package, as far as is reasonably
1706 The rationale is that there is some information conveyed
1707 by knowing the age of the file, for example, you could
1708 recognize that some documentation is very old by looking
1709 at the modification time, so it would be nice if the
1710 modification time of the upstream source would be
1716 <sect id="restrictions">
1717 <heading>Restrictions on objects in source packages</heading>
1720 The source package may not contain any hard links<footnote>
1722 This is not currently detected when building source
1723 packages, but only when extracting
1727 Hard links may be permitted at some point in the
1728 future, but would require a fair amount of
1731 </footnote>, device special files, sockets or setuid or
1732 setgid files.<footnote>
1733 Setgid directories are allowed.
1738 <sect id="debianrules">
1739 <heading>Main building script: <file>debian/rules</file></heading>
1742 This file must be an executable makefile, and contains the
1743 package-specific recipes for compiling the package and
1744 building binary package(s) from the source.
1748 It must start with the line <tt>#!/usr/bin/make -f</tt>,
1749 so that it can be invoked by saying its name rather than
1750 invoking <prgn>make</prgn> explicitly.
1754 Since an interactive <file>debian/rules</file> script makes it
1755 impossible to auto-compile that package and also makes it
1756 hard for other people to reproduce the same binary
1757 package, all <em>required targets</em> MUST be
1758 non-interactive. At a minimum, required targets are the
1759 ones called by <prgn>dpkg-buildpackage</prgn>, namely,
1760 <em>clean</em>, <em>binary</em>, <em>binary-arch</em>,
1761 <em>binary-indep</em>, and <em>build</em>. It also follows
1762 that any target that these targets depend on must also be
1767 The targets are as follows (required unless stated otherwise):
1769 <tag><tt>build</tt></tag>
1772 The <tt>build</tt> target should perform all the
1773 configuration and compilation of the package.
1774 If a package has an interactive pre-build
1775 configuration routine, the Debianized source package
1776 must either be built after this has taken place (so
1777 that the binary package can be built without rerunning
1778 the configuration) or the configuration routine
1779 modified to become non-interactive. (The latter is
1780 preferable if there are architecture-specific features
1781 detected by the configuration routine.)
1785 For some packages, notably ones where the same
1786 source tree is compiled in different ways to produce
1787 two binary packages, the <tt>build</tt> target
1788 does not make much sense. For these packages it is
1789 good enough to provide two (or more) targets
1790 (<tt>build-a</tt> and <tt>build-b</tt> or whatever)
1791 for each of the ways of building the package, and a
1792 <tt>build</tt> target that does nothing. The
1793 <tt>binary</tt> target will have to build the
1794 package in each of the possible ways and make the
1795 binary package out of each.
1799 The <tt>build</tt> target must not do anything
1800 that might require root privilege.
1804 The <tt>build</tt> target may need to run the
1805 <tt>clean</tt> target first - see below.
1809 When a package has a configuration and build routine
1810 which takes a long time, or when the makefiles are
1811 poorly designed, or when <tt>build</tt> needs to
1812 run <tt>clean</tt> first, it is a good idea to
1813 <tt>touch build</tt> when the build process is
1814 complete. This will ensure that if <tt>debian/rules
1815 build</tt> is run again it will not rebuild the whole
1817 Another common way to do this is for <tt>build</tt>
1818 to depend on <prgn>build-stamp</prgn> and to do
1819 nothing else, and for the <prgn>build-stamp</prgn>
1820 target to do the building and to <tt>touch
1821 build-stamp</tt> on completion. This is
1822 especially useful if the build routine creates a
1823 file or directory called <tt>build</tt>; in such a
1824 case, <tt>build</tt> will need to be listed as
1825 a phony target (i.e., as a dependency of the
1826 <tt>.PHONY</tt> target). See the documentation of
1827 <prgn>make</prgn> for more information on phony
1833 <tag><tt>build-arch</tt> (optional),
1834 <tt>build-indep</tt> (optional)
1838 A package may also provide both of the targets
1839 <tt>build-arch</tt> and <tt>build-indep</tt>.
1840 The <tt>build-arch</tt> target, if provided, should
1841 perform all the configuration and compilation required
1842 for producing all architecture-dependant binary packages
1843 (those packages for which the body of the
1844 <tt>Architecture</tt> field in <tt>debian/control</tt>
1845 is not <tt>all</tt>).
1846 Similarly, the <tt>build-indep</tt> target, if
1847 provided, should perform all the configuration and
1848 compilation required for producing all
1849 architecture-independent binary packages
1850 (those packages for which the body of the
1851 <tt>Architecture</tt> field in <tt>debian/control</tt>
1853 The <tt>build</tt> target should depend on those of the
1854 targets <tt>build-arch</tt> and <tt>build-indep</tt> that
1855 are provided in the rules file.
1859 If one or both of the targets <tt>build-arch</tt> and
1860 <tt>build-indep</tt> are not provided, then invoking
1861 <file>debian/rules</file> with one of the not-provided
1862 targets as arguments should produce a exit status code
1863 of 2. Usually this is provided automatically by make
1864 if the target is missing.
1868 The <tt>build-arch</tt> and <tt>build-indep</tt> targets
1869 must not do anything that might require root privilege.
1873 <tag><tt>binary</tt>, <tt>binary-arch</tt>,
1874 <tt>binary-indep</tt>
1878 The <tt>binary</tt> target must be all that is
1879 necessary for the user to build the binary package(s)
1880 produced from this source package. It is
1881 split into two parts: <prgn>binary-arch</prgn> builds
1882 the binary packages which are specific to a particular
1883 architecture, and <tt>binary-indep</tt> builds
1884 those which are not.
1887 <tt>binary</tt> may be (and commonly is) a target with
1888 no commands which simply depends on
1889 <tt>binary-arch</tt> and <tt>binary-indep</tt>.
1892 Both <tt>binary-*</tt> targets should depend on the
1893 <tt>build</tt> target, or on the appropriate
1894 <tt>build-arch</tt> or <tt>build-indep</tt> target, if
1895 provided, so that the package is built if it has not
1896 been already. It should then create the relevant
1897 binary package(s), using <prgn>dpkg-gencontrol</prgn> to
1898 make their control files and <prgn>dpkg-deb</prgn> to
1899 build them and place them in the parent of the top
1904 Both the <tt>binary-arch</tt> and
1905 <tt>binary-indep</tt> targets <em>must</em> exist.
1906 If one of them has nothing to do (which will always be
1907 the case if the source generates only a single binary
1908 package, whether architecture-dependent or not), it
1909 must still exist and must always succeed.
1913 The <tt>binary</tt> targets must be invoked as
1915 The <prgn>fakeroot</prgn> package often allows one
1916 to build a package correctly even without being
1922 <tag><tt>clean</tt></tag>
1925 This must undo any effects that the <tt>build</tt>
1926 and <tt>binary</tt> targets may have had, except
1927 that it should leave alone any output files created in
1928 the parent directory by a run of a <tt>binary</tt>
1933 If a <tt>build</tt> file is touched at the end of
1934 the <tt>build</tt> target, as suggested above, it
1935 should be removed as the first action that
1936 <tt>clean</tt> performs, so that running
1937 <tt>build</tt> again after an interrupted
1938 <tt>clean</tt> doesn't think that everything is
1943 The <tt>clean</tt> target may need to be
1944 invoked as root if <tt>binary</tt> has been
1945 invoked since the last <tt>clean</tt>, or if
1946 <tt>build</tt> has been invoked as root (since
1947 <tt>build</tt> may create directories, for
1952 <tag><tt>get-orig-source</tt> (optional)</tag>
1955 This target fetches the most recent version of the
1956 original source package from a canonical archive site
1957 (via FTP or WWW, for example), does any necessary
1958 rearrangement to turn it into the original source
1959 tar file format described below, and leaves it in the
1964 This target may be invoked in any directory, and
1965 should take care to clean up any temporary files it
1970 This target is optional, but providing it if
1971 possible is a good idea.
1977 The <tt>build</tt>, <tt>binary</tt> and
1978 <tt>clean</tt> targets must be invoked with the current
1979 directory being the package's top-level directory.
1984 Additional targets may exist in <file>debian/rules</file>,
1985 either as published or undocumented interfaces or for the
1986 package's internal use.
1990 The architectures we build on and build for are determined
1991 by <prgn>make</prgn> variables using the utility
1992 <qref id="pkg-dpkgarch"><prgn>dpkg-architecture</prgn></qref>.
1993 You can determine the
1994 Debian architecture and the GNU style architecture
1995 specification string for the build machine (the machine type
1996 we are building on) as well as for the host machine (the
1997 machine type we are building for). Here is a list of
1998 supported <prgn>make</prgn> variables:
1999 <list compact="compact">
2001 <tt>DEB_*_ARCH</tt> (the Debian architecture)
2004 <tt>DEB_*_GNU_TYPE</tt> (the GNU style architecture
2005 specification string)
2008 <tt>DEB_*_GNU_CPU</tt> (the CPU part of
2009 <tt>DEB_*_GNU_TYPE</tt>)
2012 <tt>DEB_*_GNU_SYSTEM</tt> (the System part of
2013 <tt>DEB_*_GNU_TYPE</tt>)
2015 where <tt>*</tt> is either <tt>BUILD</tt> for specification of
2016 the build machine or <tt>HOST</tt> for specification of the
2021 Backward compatibility can be provided in the rules file
2022 by setting the needed variables to suitable default
2023 values; please refer to the documentation of
2024 <prgn>dpkg-architecture</prgn> for details.
2028 It is important to understand that the <tt>DEB_*_ARCH</tt>
2029 string only determines which Debian architecture we are
2030 building on or for. It should not be used to get the CPU
2031 or system information; the GNU style variables should be
2036 <!-- FIXME: section pkg-srcsubstvars is the same as substvars -->
2037 <sect id="substvars">
2038 <heading>Variable substitutions: <file>debian/substvars</file></heading>
2041 When <prgn>dpkg-gencontrol</prgn>,
2042 <prgn>dpkg-genchanges</prgn> and <prgn>dpkg-source</prgn>
2043 generate control files they perform variable substitutions
2044 on their output just before writing it. Variable
2045 substitutions have the form <tt>${<var>variable</var>}</tt>.
2046 The optional file <file>debian/substvars</file> contains
2047 variable substitutions to be used; variables can also be set
2048 directly from <file>debian/rules</file> using the <tt>-V</tt>
2049 option to the source packaging commands, and certain
2050 predefined variables are also available.
2054 The <file>debian/substvars</file> file is usually generated and
2055 modified dynamically by <file>debian/rules</file> targets, in
2056 which case it must be removed by the <tt>clean</tt> target.
2060 See <manref name="dpkg-source" section="1"> for full
2061 details about source variable substitutions, including the
2062 format of <file>debian/substvars</file>.</p>
2065 <sect id="debianfiles">
2066 <heading>Generated files list: <file>debian/files</file></heading>
2069 This file is not a permanent part of the source tree; it
2070 is used while building packages to record which files are
2071 being generated. <prgn>dpkg-genchanges</prgn> uses it
2072 when it generates a <file>.changes</file> file.
2076 It should not exist in a shipped source package, and so it
2077 (and any backup files or temporary files such as
2078 <file>files.new</file><footnote>
2079 <file>files.new</file> is used as a temporary file by
2080 <prgn>dpkg-gencontrol</prgn> and
2081 <prgn>dpkg-distaddfile</prgn> - they write a new
2082 version of <tt>files</tt> here before renaming it,
2083 to avoid leaving a corrupted copy if an error
2085 </footnote>) should be removed by the
2086 <tt>clean</tt> target. It may also be wise to
2087 ensure a fresh start by emptying or removing it at the
2088 start of the <tt>binary</tt> target.
2092 When <prgn>dpkg-gencontrol</prgn> is run for a binary
2093 package, it adds an entry to <file>debian/files</file> for the
2094 <file>.deb</file> file that will be created when <tt>dpkg-deb
2095 --build</tt> is run for that binary package. So for most
2096 packages all that needs to be done with this file is to
2097 delete it in the <tt>clean</tt> target.
2101 If a package upload includes files besides the source
2102 package and any binary packages whose control files were
2103 made with <prgn>dpkg-gencontrol</prgn> then they should be
2104 placed in the parent of the package's top-level directory
2105 and <prgn>dpkg-distaddfile</prgn> should be called to add
2106 the file to the list in <file>debian/files</file>.</p>
2112 <chapt id="controlfields">
2113 <heading>Control files and their fields</heading>
2116 The package management system manipulates data represented in
2117 a common format, known as <em>control data</em>, stored in
2118 <em>control files</em>.
2119 Control files are used for source packages, binary packages and
2120 the <file>.changes</file> files which control the installation
2121 of uploaded files<footnote>
2122 <prgn>dpkg</prgn>'s internal databases are in a similar
2127 <sect id="controlsyntax">
2128 <heading>Syntax of control files</heading>
2131 A control file consists of one or more paragraphs of
2133 The paragraphs are also sometimes referred to as stanzas.
2135 The paragraphs are separated by blank lines. Some control
2136 files allow only one paragraph; others allow several, in
2137 which case each paragraph usually refers to a different
2138 package. (For example, in source packages, the first
2139 paragraph refers to the source package, and later paragraphs
2140 refer to binary packages generated from the source.)
2144 Each paragraph consists of a series of data fields; each
2145 field consists of the field name, followed by a colon and
2146 then the data/value associated with that field. It ends at
2147 the end of the line. Horizontal whitespace (spaces and
2148 tabs) may occur immediately before or after the value and is
2149 ignored there; it is conventional to put a single space
2150 after the colon. For example, a field might be:
2151 <example compact="compact">
2154 the field name is <tt>Package</tt> and the field value
2159 Some fields' values may span several lines; in this case
2160 each continuation line must start with a space or a tab.
2161 Any trailing spaces or tabs at the end of individual
2162 lines of a field value are ignored.
2166 Except where otherwise stated, only a single line of data is
2167 allowed and whitespace is not significant in a field body.
2168 Whitespace must not appear inside names (of packages,
2169 architectures, files or anything else) or version numbers,
2170 or between the characters of multi-character version
2175 Field names are not case-sensitive, but it is usual to
2176 capitalize the field names using mixed case as shown below.
2180 Blank lines, or lines consisting only of spaces and tabs,
2181 are not allowed within field values or between fields - that
2182 would mean a new paragraph.
2187 <sect id="sourcecontrolfiles">
2188 <heading>Source package control files -- <file>debian/control</file></heading>
2191 The <file>debian/control</file> file contains the most vital
2192 (and version-independent) information about the source package
2193 and about the binary packages it creates.
2197 The first paragraph of the control file contains information about
2198 the source package in general. The subsequent sets each describe a
2199 binary package that the source tree builds.
2203 The fields in the general paragraph (the first one, for the source
2206 <list compact="compact">
2207 <item><qref id="f-Source"><tt>Source</tt></qref> (mandatory)</item>
2208 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
2209 <item><qref id="f-Section"><tt>Section</tt></qref> (recommended)</item>
2210 <item><qref id="f-Priority"><tt>Priority</tt></qref> (recommended)</item>
2211 <item><qref id="sourcebinarydeps"><tt>Build-Depends</tt> et al</qref></item>
2212 <item><qref id="f-Standards-Version"><tt>Standards-Version</tt></qref> (recommended)</item>
2217 The fields in the binary package paragraphs are:
2219 <list compact="compact">
2220 <item><qref id="f-Package"><tt>Package</tt></qref> (mandatory)</item>
2221 <item><qref id="f-Architecture"><tt>Architecture</tt></qref> (mandatory)</item>
2222 <item><qref id="f-Section"><tt>Section</tt></qref> (recommended)</item>
2223 <item><qref id="f-Priority"><tt>Priority</tt></qref> (recommended)</item>
2224 <item><qref id="f-Essential"><tt>Essential</tt></qref></item>
2225 <item><qref id="binarydeps"><tt>Depends</tt> et al</qref></item>
2226 <item><qref id="f-Description"><tt>Description</tt></qref> (mandatory)</item>
2231 The syntax and semantics of the fields are described below.
2237 These fields are used by <prgn>dpkg-gencontrol</prgn> to
2238 generate control files for binary packages (see below), by
2239 <prgn>dpkg-genchanges</prgn> to generate the
2240 <tt>.changes</tt> file to accompany the upload, and by
2241 <prgn>dpkg-source</prgn> when it creates the <file>.dsc</file>
2242 source control file as part of a source archive.
2246 The fields here may contain variable references - their
2247 values will be substituted by <prgn>dpkg-gencontrol</prgn>,
2248 <prgn>dpkg-genchanges</prgn> or <prgn>dpkg-source</prgn>
2249 when they generate output control files.
2250 See <ref id="substvars"> for details.
2255 <sect id="binarycontrolfiles">
2256 <heading>Binary package control files -- <file>DEBIAN/control</file></heading>
2259 The <file>DEBIAN/control</file> file contains the most vital
2260 (and version-dependent) information about a binary package.
2264 The fields in this file are:
2266 <list compact="compact">
2267 <item><qref id="f-Package"><tt>Package</tt></qref> (mandatory)</item>
2268 <item><qref id="f-Source"><tt>Source</tt></qref></item>
2269 <item><qref id="f-Version"><tt>Version</tt></qref> (mandatory)</item>
2270 <item><qref id="f-Section"><tt>Section</tt></qref> (recommended)</item>
2271 <item><qref id="f-Priority"><tt>Priority</tt></qref> (recommended)</item>
2272 <item><qref id="f-Architecture"><tt>Architecture</tt></qref> (mandatory)</item>
2273 <item><qref id="f-Essential"><tt>Essential</tt></qref></item>
2274 <item><qref id="binarydeps"><tt>Depends</tt> et al</qref></item>
2275 <item><qref id="f-Installed-Size"><tt>Installed-Size</tt></qref></item>
2276 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
2277 <item><qref id="f-Description"><tt>Description</tt></qref> (mandatory)</item>
2282 <sect id="debiansourcecontrolfiles">
2283 <heading>Debian source control files -- <tt>.dsc</tt></heading>
2286 This file contains a series of fields, identified and
2287 separated just like the fields in the control file of
2288 a binary package. The fields are listed below; their
2289 syntax is described above, in <ref id="pkg-controlfields">.
2291 <list compact="compact">
2292 <item><qref id="f-Source"><tt>Source</tt></qref> (mandatory)</item>
2293 <item><qref id="f-Version"><tt>Version</tt></qref> (mandatory)</item>
2294 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
2295 <item><qref id="f-Binary"><tt>Binary</tt></qref></item>
2296 <item><qref id="f-Architecture"><tt>Architecture</tt></qref></item>
2297 <item><qref id="sourcebinarydeps"><tt>Build-Depends</tt> et al</qref></item>
2298 <item><qref id="f-Standards-Version"><tt>Standards-Version</tt></qref> (recommended)</item>
2299 <item><qref id="f-Files"><tt>Files</tt></qref> (mandatory)</item>
2304 The source package control file is generated by
2305 <prgn>dpkg-source</prgn> when it builds the source
2306 archive, from other files in the source package,
2307 described above. When unpacking, it is checked against
2308 the files and directories in the other parts of the
2314 <sect id="debianchangesfiles">
2315 <heading>Debian changes files -- <file>.changes</file></heading>
2318 The .changes files are used by the Debian archive maintenance
2319 software to process updates to packages. They contain one
2320 paragraph which contains information from the
2321 <tt>debian/control</tt> file and other data about the
2322 source package gathered via <tt>debian/changelog</tt>
2323 and <tt>debian/rules</tt>.
2327 The fields in this file are:
2329 <list compact="compact">
2330 <item><qref id="f-Format"><tt>Format</tt></qref> (mandatory)</item>
2331 <item><qref id="f-Date"><tt>Date</tt></qref> (mandatory)</item>
2332 <item><qref id="f-Source"><tt>Source</tt></qref> (mandatory)</item>
2333 <item><qref id="f-Binary"><tt>Binary</tt></qref> (mandatory)</item>
2334 <item><qref id="f-Architecture"><tt>Architecture</tt></qref> (mandatory)</item>
2335 <item><qref id="f-Version"><tt>Version</tt></qref> (mandatory)</item>
2336 <item><qref id="f-Distribution"><tt>Distribution</tt></qref> (mandatory)</item>
2337 <item><qref id="f-Urgency"><tt>Urgency</tt></qref> (recommended)</item>
2338 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
2339 <item><qref id="f-Changed-By"><tt>Changed-By</tt></qref></item>
2340 <item><qref id="f-Description"><tt>Description</tt></qref> (mandatory)</item>
2341 <item><qref id="f-Closes"><tt>Closes</tt></qref></item>
2342 <item><qref id="f-Changes"><tt>Changes</tt></qref> (mandatory)</item>
2343 <item><qref id="f-Files"><tt>Files</tt></qref> (mandatory)</item>
2348 <sect id="controlfieldslist">
2349 <heading>List of fields</heading>
2351 <sect1 id="f-Source">
2352 <heading><tt>Source</tt></heading>
2355 This field identifies the source package name.
2359 In a main source control information, a <file>.changes</file>
2360 or a <file>.dsc</file> file this may contain only the name
2361 of the source package.
2365 In the control file of a binary package it may be followed
2366 by a version number in parentheses<footnote>
2367 It is customary to leave a space after the package name
2368 if a version number is specified.
2370 This version number may be omitted (and is, by
2371 <prgn>dpkg-gencontrol</prgn>) if it has the same value as
2372 the <tt>Version</tt> field of the binary package in
2373 question. The field itself may be omitted from a binary
2374 package control file when the source package has the same
2375 name and version as the binary package.
2379 <sect1 id="f-Maintainer">
2380 <heading><tt>Maintainer</tt></heading>
2383 The package maintainer's name and email address. The name
2384 should come first, then the email address inside angle
2385 brackets <tt><></tt> (in RFC822 format).
2389 If the maintainer's name contains a full stop then the
2390 whole field will not work directly as an email address due
2391 to a misfeature in the syntax specified in RFC822; a
2392 program using this field as an address must check for this
2393 and correct the problem if necessary (for example by
2394 putting the name in round brackets and moving it to the
2395 end, and bringing the email address forward).
2399 <sect1 id="f-Changed-By">
2400 <heading><tt>Changed-By</tt></heading>
2403 The name and email address of the person who changed the
2404 said package. Usually the name of the maintainer.
2405 All the rules for the Maintainer field apply here, too.
2409 <sect1 id="f-Section">
2410 <heading><tt>Section</tt></heading>
2413 This field specifies an application area into which the package
2414 has been classified. See <ref id="subsections">.
2418 When it appears in the <file>debian/control</file> file,
2419 it gives the value for the subfield of the same name in
2420 the <tt>Files</tt> field of the <file>.changes</file> file.
2421 It also gives the default for the same field in the binary
2426 By default, <prgn>dpkg-gencontrol</prgn> does not include this
2427 field in the control file of a binary package - use the
2428 <tt>-is</tt> (or <tt>-isp</tt>) options to achieve this effect.
2432 <sect1 id="f-Priority">
2433 <heading><tt>Priority</tt></heading>
2436 This field represents how important that it is that the user
2437 have the package installed. See <ref id="priorities">.
2441 When it appears in the <file>debian/control</file> file,
2442 it gives the value for the subfield of the same name in
2443 the <tt>Files</tt> field of the <file>.changes</file> file.
2444 It also gives the default for the same field in the binary
2449 By default, <prgn>dpkg-gencontrol</prgn> does not include this
2450 field in the control file of a binary package - use the
2451 <tt>-ip</tt> (or <tt>-isp</tt>) options to achieve this effect.
2455 <sect1 id="f-Package">
2456 <heading><tt>Package</tt></heading>
2459 The name of the binary package.
2463 Package names must consist only of lower case letters
2464 (<tt>a-z</tt>), digits (<tt>0-9</tt>), plus (<tt>+</tt>)
2465 and minus (<tt>-</tt>) signs, and periods (<tt>.</tt>).
2466 They must be at least two characters long and must start
2467 with an alphanumeric character.
2471 <sect1 id="f-Architecture">
2472 <heading><tt>Architecture</tt></heading>
2475 This is the architecture string; it is a single word for
2476 the Debian architecture. The special value <tt>all</tt>
2477 indicates that the package is architecture-independent.
2481 In the main <file>debian/control</file> file in the source
2482 package, or in the source package control file
2483 <file>.dsc</file>, a list of architectures (separated by
2484 spaces) is also allowed, as is the special value
2485 <tt>any</tt>. A list indicates that the source will build
2486 an architecture-dependent package, and will only work
2487 correctly on the listed architectures. <tt>any</tt>
2488 indicates that though the source package isn't dependent
2489 on any particular architecture and should compile fine on
2490 any one, the binary package(s) produced are not
2491 architecture-independent but will instead be specific to
2492 whatever the current build architecture is.
2496 In a <file>.changes</file> file the <tt>Architecture</tt>
2497 field lists the architecture(s) of the package(s)
2498 currently being uploaded. This will be a list; if the
2499 source for the package is being uploaded too the special
2500 entry <tt>source</tt> is also present.
2504 See <ref id="debianrules"> for information how to get the
2505 architecture for the build process.
2509 <sect1 id="f-Essential">
2510 <heading><tt>Essential</tt></heading>
2513 This is a boolean field which may occur only in the
2514 control file of a binary package or in a per-package fields
2515 paragraph of a main source control data file.
2519 If set to <tt>yes</tt> then the package management system
2520 will refuse to remove the package (upgrading and replacing
2521 it is still possible). The other possible value is <tt>no</tt>,
2522 which is the same as not having the field at all.
2527 <heading>Package interrelationship fields:
2528 <tt>Depends</tt>, <tt>Pre-Depends</tt>,
2529 <tt>Recommends</tt>, <tt>Suggests</tt>, <tt>Conflicts</tt>,
2530 <tt>Provides</tt>, <tt>Replaces</tt>
2534 These fields describe the package's relationships with
2535 other packages. Their syntax and semantics are described
2536 in <ref id="relationships">.</p>
2539 <sect1 id="f-Standards-Version">
2540 <heading><tt>Standards-Version</tt></heading>
2543 The most recent version of the standards (the policy
2544 manual and associated texts) with which the package
2549 The version number has four components: major and minor
2550 version number and major and minor patch level. When the
2551 standards change in a way that requires every package to
2552 change the major number will be changed. Significant
2553 changes that will require work in many packages will be
2554 signaled by a change to the minor number. The major patch
2555 level will be changed for any change to the meaning of the
2556 standards, however small; the minor patch level will be
2557 changed when only cosmetic, typographical or other edits
2558 are made which neither change the meaning of the document
2559 nor affect the contents of packages.
2563 Thus only the first three components of the policy version
2564 are significant in the <em>Standards-Version</em> control
2565 field, and so either these three components or the all
2566 four components may be specified.<footnote>
2567 In the past, people specified the full version number
2568 in the Standards-Version field, for example "2.3.0.0".
2569 Since minor patch-level changes don't introduce new
2570 policy, it was thought it would be better to relax
2571 policy and only require the first 3 components to be
2572 specified, in this example "2.3.0". All four
2573 components may still be used if someone wishes to do so.
2579 <sect1 id="f-Version">
2580 <heading><tt>Version</tt></heading>
2583 The version number of a package. The format is:
2584 [<var>epoch</var><tt>:</tt>]<var>upstream_version</var>[<tt>-</tt><var>debian_revision</var>]
2588 The three components here are:
2590 <tag><var>epoch</var></tag>
2593 This is a single (generally small) unsigned integer. It
2594 may be omitted, in which case zero is assumed. If it is
2595 omitted then the <var>upstream_version</var> may not
2600 It is provided to allow mistakes in the version numbers
2601 of older versions of a package, and also a package's
2602 previous version numbering schemes, to be left behind.
2606 <tag><var>upstream_version</var></tag>
2609 This is the main part of the version number. It is
2610 usually the version number of the original ("upstream")
2611 package from which the <file>.deb</file> file has been made,
2612 if this is applicable. Usually this will be in the same
2613 format as that specified by the upstream author(s);
2614 however, it may need to be reformatted to fit into the
2615 package management system's format and comparison
2620 The comparison behavior of the package management system
2621 with respect to the <var>upstream_version</var> is
2622 described below. The <var>upstream_version</var>
2623 portion of the version number is mandatory.
2627 The <var>upstream_version</var> may contain only
2628 alphanumerics<footnote>
2629 Alphanumerics are <tt>A-Za-z0-9</tt> only.
2631 and the characters <tt>.</tt> <tt>+</tt> <tt>-</tt>
2632 <tt>:</tt> (full stop, plus, hyphen, colon) and should
2633 start with a digit. If there is no
2634 <var>debian_revision</var> then hyphens are not allowed;
2635 if there is no <var>epoch</var> then colons are not
2640 <tag><var>debian_revision</var></tag>
2643 This part of the version number specifies the version of
2644 the Debian package based on the upstream version. It
2645 may contain only alphanumerics and the characters
2646 <tt>+</tt> and <tt>.</tt> (plus and full stop) and is
2647 compared in the same way as the
2648 <var>upstream_version</var> is.
2652 It is optional; if it isn't present then the
2653 <var>upstream_version</var> may not contain a hyphen.
2654 This format represents the case where a piece of
2655 software was written specifically to be turned into a
2656 Debian package, and so there is only one "debianization"
2657 of it and therefore no revision indication is required.
2661 It is conventional to restart the
2662 <var>debian_revision</var> at <tt>1</tt> each time the
2663 <var>upstream_version</var> is increased.
2667 The package management system will break the version
2668 number apart at the last hyphen in the string (if there
2669 is one) to determine the <var>upstream_version</var> and
2670 <var>debian_revision</var>. The absence of a
2671 <var>debian_revision</var> compares earlier than the
2672 presence of one (but note that the
2673 <var>debian_revision</var> is the least significant part
2674 of the version number).
2681 The <var>upstream_version</var> and <var>debian_revision</var>
2682 parts are compared by the package management system using the
2687 The strings are compared from left to right.
2691 First the initial part of each string consisting entirely of
2692 non-digit characters is determined. These two parts (one of
2693 which may be empty) are compared lexically. If a difference
2694 is found it is returned. The lexical comparison is a
2695 comparison of ASCII values modified so that all the letters
2696 sort earlier than all the non-letters.
2700 Then the initial part of the remainder of each string which
2701 consists entirely of digit characters is determined. The
2702 numerical values of these two parts are compared, and any
2703 difference found is returned as the result of the comparison.
2704 For these purposes an empty string (which can only occur at
2705 the end of one or both version strings being compared) counts
2710 These two steps (comparing and removing initial non-digit
2711 strings and initial digit strings) are repeated until a
2712 difference is found or both strings are exhausted.
2716 Note that the purpose of epochs is to allow us to leave behind
2717 mistakes in version numbering, and to cope with situations
2718 where the version numbering scheme changes. It is
2719 <em>not</em> intended to cope with version numbers containing
2720 strings of letters which the package management system cannot
2721 interpret (such as <tt>ALPHA</tt> or <tt>pre-</tt>), or with
2722 silly orderings (the author of this manual has heard of a
2723 package whose versions went <tt>1.1</tt>, <tt>1.2</tt>,
2724 <tt>1.3</tt>, <tt>1</tt>, <tt>2.1</tt>, <tt>2.2</tt>,
2725 <tt>2</tt> and so forth).
2729 <sect1 id="f-Description">
2730 <heading><tt>Description</tt></heading>
2733 In a source or binary control file, the <tt>Description</tt>
2734 field contains a description of the binary package, consisting
2735 of two parts, the synopsis or the short description, and the
2736 long description. The field's format is as follows:
2741 Description: <single line synopsis>
2742 <extended description over several lines>
2747 The lines in the extended description can have these formats:
2753 Those starting with a single space are part of a paragraph.
2754 Successive lines of this form will be word-wrapped when
2755 displayed. The leading space will usually be stripped off.
2759 Those starting with two or more spaces. These will be
2760 displayed verbatim. If the display cannot be panned
2761 horizontally, the displaying program will linewrap them "hard"
2762 (i.e., without taking account of word breaks). If it can they
2763 will be allowed to trail off to the right. None, one or two
2764 initial spaces may be deleted, but the number of spaces
2765 deleted from each line will be the same (so that you can have
2766 indenting work correctly, for example).
2770 Those containing a single space followed by a single full stop
2771 character. These are rendered as blank lines. This is the
2772 <em>only</em> way to get a blank line<footnote>
2773 Completely empty lines will not be rendered as blank lines.
2774 Instead, they will cause the parser to think you're starting
2775 a whole new record in the control file, and will therefore
2776 likely abort with an error.
2781 Those containing a space, a full stop and some more characters.
2782 These are for future expansion. Do not use them.
2788 Do not use tab characters. Their effect is not predictable.
2792 See <ref id="descriptions"> for further information on this.
2796 In a <file>.changes</file> file, the <tt>Description</tt> field
2797 contains a summary of the descriptions for the packages being
2802 The part of the field before the first newline is empty;
2803 thereafter each line has the name of a binary package and
2804 the summary description line from that binary package.
2805 Each line is indented by one space.
2810 <sect1 id="f-Distribution">
2811 <heading><tt>Distribution</tt></heading>
2814 In a <file>.changes</file> file or parsed changelog output
2815 this contains the (space-separated) name(s) of the
2816 distribution(s) where this version of the package should
2817 be installed. Valid distributions are determined by the
2818 archive maintainers.<footnote>
2819 Current distribution names are:
2820 <taglist compact="compact">
2821 <tag><em>stable</em></tag>
2823 This is the current "released" version of Debian
2824 GNU/Linux. Once the distribution is
2825 <em>stable</em> only security fixes and other
2826 major bug fixes are allowed. When changes are
2827 made to this distribution, the release number is
2828 increased (for example: 2.2r1 becomes 2.2r2 then
2832 <tag><em>unstable</em></tag>
2834 This distribution value refers to the
2835 <em>developmental</em> part of the Debian
2836 distribution tree. New packages, new upstream
2837 versions of packages and bug fixes go into the
2838 <em>unstable</em> directory tree. Download from
2839 this distribution at your own risk.
2842 <tag><em>testing</em></tag>
2844 This distribution value refers to the
2845 <em>testing</em> part of the Debian distribution
2846 tree. It receives its packages from the
2847 unstable distribution after a short time lag to
2848 ensure that there are no major issues with the
2849 unstable packages. It is less prone to breakage
2850 than unstable, but still risky. It is not
2851 possible to upload packages directly to
2855 <tag><em>frozen</em></tag>
2857 From time to time, the <em>testing</em>
2858 distribution enters a state of "code-freeze" in
2859 anticipation of release as a <em>stable</em>
2860 version. During this period of testing only
2861 fixes for existing or newly-discovered bugs will
2862 be allowed. The exact details of this stage are
2863 determined by the Release Manager.
2866 <tag><em>experimental</em></tag>
2868 The packages with this distribution value are
2869 deemed by their maintainers to be high
2870 risk. Oftentimes they represent early beta or
2871 developmental packages from various sources that
2872 the maintainers want people to try, but are not
2873 ready to be a part of the other parts of the
2874 Debian distribution tree. Download at your own
2880 You should list <em>all</em> distributions that the
2881 package should be installed into.
2885 More information is available in the Debian Developer's
2886 Reference, section "The Debian archive".
2893 <heading><tt>Date</tt></heading>
2896 This field includes the date the package was built or last edited.
2900 The value of this field is usually extracted from the
2901 <file>debian/changelog</file> file - see
2902 <ref id="dpkgchangelog">).
2906 <sect1 id="f-Format">
2907 <heading><tt>Format</tt></heading>
2910 This field specifies a format revision for the file.
2911 The most current format described in the Policy Manual
2912 is version <strong>1.5</strong>. The syntax of the
2913 format value is the same as that of a package version
2914 number except that no epoch or Debian revision is allowed
2915 - see <ref id="f-Version">.
2919 <sect1 id="f-Urgency">
2920 <heading><tt>Urgency</tt></heading>
2923 This is a description of how important it is to upgrade to
2924 this version from previous ones. It consists of a single
2925 keyword usually taking one of the values <tt>low</tt>,
2926 <tt>medium</tt> or <tt>high</tt> (not case-sensitive)
2927 followed by an optional commentary (separated by a space)
2928 which is usually in parentheses. For example:
2931 Urgency: low (HIGH for users of diversions)
2937 The value of this field is usually extracted from the
2938 <file>debian/changelog</file> file - see
2939 <ref id="dpkgchangelog">.
2943 <sect1 id="f-Changes">
2944 <heading><tt>Changes</tt></heading>
2947 This field contains the human-readable changes data, describing
2948 the differences between the last version and the current one.
2952 There should be nothing in this field before the first
2953 newline; all the subsequent lines must be indented by at
2954 least one space; blank lines must be represented by a line
2955 consiting only of a space and a full stop.
2959 The value of this field is usually extracted from the
2960 <file>debian/changelog</file> file - see
2961 <ref id="dpkgchangelog">).
2965 Each version's change information should be preceded by a
2966 "title" line giving at least the version, distribution(s)
2967 and urgency, in a human-readable way.
2971 If data from several versions is being returned the entry
2972 for the most recent version should be returned first, and
2973 entries should be separated by the representation of a
2974 blank line (the "title" line may also be followed by the
2975 representation of blank line).
2979 <sect1 id="f-Binary">
2980 <heading><tt>Binary</tt></heading>
2983 This field is a list of binary packages.
2987 When it appears in the <file>.dsc</file> file it is the list
2988 of binary packages which a source package can produce. It
2989 does not necessarily produce all of these binary packages
2990 for every architecture. The source control file doesn't
2991 contain details of which architectures are appropriate for
2992 which of the binary packages.
2996 When it appears in a <file>.changes</file> file it lists the
2997 names of the binary packages actually being uploaded.
3001 The syntax is a list of binary packages separated by
3003 A space after each comma is conventional.
3004 </footnote>. Currently the packages must be separated using
3005 only spaces in the <file>.changes</file> file.
3009 <sect1 id="f-Installed-Size">
3010 <heading><tt>Installed-Size</tt></heading>
3013 This field appears in the control files of binary
3014 packages, and in the <file>Packages</file> files. It gives
3015 the total amount of disk space required to install the
3020 The disk space is represented in kilobytes as a simple
3025 <sect1 id="f-Files">
3026 <heading><tt>Files</tt></heading>
3029 This field contains a list of files with information about
3030 each one. The exact information and syntax varies with
3031 the context. In all cases the part of the field
3032 contents on the same line as the field name is empty. The
3033 remainder of the field is one line per file, each line
3034 being indented by one space and containing a number of
3035 sub-fields separated by spaces.
3039 In the <file>.dsc</file> file, each line contains the MD5
3040 checksum, size and filename of the tar file and (if applicable)
3041 diff file which make up the remainder of the source
3043 That is, the parts which are not the <tt>.dsc</tt>.
3045 The exact forms of the filenames are described
3046 in <ref id="pkg-sourcearchives">.
3050 In the <file>.changes</file> file this contains one line per
3051 file being uploaded. Each line contains the MD5 checksum,
3052 size, section and priority and the filename.
3053 The <qref id="f-Section">section</qref>
3054 and <qref id="f-Priority">priority</qref>
3055 are the values of the corresponding fields in
3056 the main source control file. If no section or priority is
3057 specified then <tt>-</tt> should be used, though section
3058 and priority values must be specified for new packages to
3059 be installed properly.
3063 The special value <tt>byhand</tt> for the section in a
3064 <tt>.changes</tt> file indicates that the file in question
3065 is not an ordinary package file and must by installed by
3066 hand by the distribution maintainers. If the section is
3067 <tt>byhand</tt> the priority should be <tt>-</tt>.
3071 If a new Debian revision of a package is being shipped and
3072 no new original source archive is being distributed the
3073 <tt>.dsc</tt> must still contain the <tt>Files</tt> field
3074 entry for the original source archive
3075 <file><var>package</var>-<var>upstream-version</var>.orig.tar.gz</file>,
3076 but the <file>.changes</file> file should leave it out. In
3077 this case the original source archive on the distribution
3078 site must match exactly, byte-for-byte, the original
3079 source archive which was used to generate the
3080 <file>.dsc</file> file and diff which are being uploaded.</p>
3083 <sect1 id="f-Closes">
3084 <heading><tt>Closes</tt></heading>
3087 A space-separated list of bug report numbers that the upload
3088 governed by the .changes file closes.
3095 <heading>User-defined fields</heading>
3098 Additional user-defined fields may be added to the
3099 source package control file. Such fields will be
3100 ignored, and not copied to (for example) binary or
3101 source package control files or upload control files.
3105 If you wish to add additional unsupported fields to
3106 these output files you should use the mechanism
3111 Fields in the main source control information file with
3112 names starting <tt>X</tt>, followed by one or more of
3113 the letters <tt>BCS</tt> and a hyphen <tt>-</tt>, will
3114 be copied to the output files. Only the part of the
3115 field name after the hyphen will be used in the output
3116 file. Where the letter <tt>B</tt> is used the field
3117 will appear in binary package control files, where the
3118 letter <tt>S</tt> is used in source package control
3119 files and where <tt>C</tt> is used in upload control
3120 (<tt>.changes</tt>) files.
3124 For example, if the main source information control file
3127 XBS-Comment: I stand between the candle and the star.
3129 then the binary and source package control files will contain the
3132 Comment: I stand between the candle and the star.
3141 <chapt id="maintainerscripts">
3142 <heading>Package maintainer scripts and installation procedure</heading>
3145 <heading>Introduction to package maintainer scripts</heading>
3148 It is possible to supply scripts as part of a package which
3149 the package management system will run for you when your
3150 package is installed, upgraded or removed.
3154 These scripts are the files <prgn>preinst</prgn>,
3155 <prgn>postinst</prgn>, <prgn>prerm</prgn> and <prgn>postrm</prgn> in the
3156 control area of the package. They must be proper executable
3157 files; if they are scripts (which is recommended), they must
3158 start with the usual <tt>#!</tt> convention. They should be
3159 readable and executable by anyone, and not world-writable.
3163 The package management system looks at the exit status from
3164 these scripts. It is important that they exit with a
3165 non-zero status if there is an error, so that the package
3166 management system can stop its processing. For shell
3167 scripts this means that you <em>almost always</em> need to
3168 use <tt>set -e</tt> (this is usually true when writing shell
3169 scripts, in fact). It is also important, of course, that
3170 they don't exit with a non-zero status if everything went
3175 When a package is upgraded a combination of the scripts from
3176 the old and new packages is called during the upgrade
3177 procedure. If your scripts are going to be at all
3178 complicated you need to be aware of this, and may need to
3179 check the arguments to your scripts.
3183 Broadly speaking the <prgn>preinst</prgn> is called before
3184 (a particular version of) a package is installed, and the
3185 <prgn>postinst</prgn> afterwards; the <prgn>prerm</prgn>
3186 before (a version of) a package is removed and the
3187 <prgn>postrm</prgn> afterwards.
3191 Programs called from maintainer scripts should not normally
3192 have a path prepended to them. Before installation is
3193 started, the package management system checks to see if the
3194 programs <prgn>ldconfig</prgn>,
3195 <prgn>start-stop-daemon</prgn>, <prgn>install-info</prgn>,
3196 and <prgn>update-rc.d</prgn> can be found via the
3197 <tt>PATH</tt> environment variable. Those programs, and any
3198 other program that one would expect to be on the
3199 <tt>PATH</tt>, should thus be invoked without an absolute
3200 pathname. Maintainer scripts should also not reset the
3201 <tt>PATH</tt>, though they might choose to modify it by
3202 prepending or appending package-specific directories. These
3203 considerations really apply to all shell scripts.</p>
3206 <sect id="idempotency">
3207 <heading>Maintainer scripts Idempotency</heading>
3210 It is necessary for the error recovery procedures that the
3211 scripts be idempotent. This means that if it is run
3212 successfully, and then it is called again, it doesn't bomb
3213 out or cause any harm, but just ensures that everything is
3214 the way it ought to be. If the first call failed, or
3215 aborted half way through for some reason, the second call
3216 should merely do the things that were left undone the first
3217 time, if any, and exit with a success status if everything
3219 This is so that if an error occurs, the user interrupts
3220 <prgn>dpkg</prgn> or some other unforeseen circumstance
3221 happens you don't leave the user with a badly-broken
3222 package when <prgn>dpkg</prgn> attempts to repeat the
3228 <sect id="controllingterminal">
3229 <heading>Controlling terminal for maintainer scripts</heading>
3232 The maintainer scripts are guaranteed to run with a
3233 controlling terminal and can interact with the user.
3234 If they need to prompt for passwords, do full-screen
3235 interaction or something similar you should do these
3236 things to and from <file>/dev/tty</file>, since
3237 <prgn>dpkg</prgn> will at some point redirect scripts'
3238 standard input and output so that it can log the
3239 installation process. Likewise, because these scripts
3240 may be executed with standard output redirected into a
3241 pipe for logging purposes, Perl scripts should set
3242 unbuffered output by setting <tt>$|=1</tt> so that the
3243 output is printed immediately rather than being
3248 Each script should return a zero exit status for
3249 success, or a nonzero one for failure.
3253 <sect id="mscriptsinstact"><heading>Summary of ways maintainer
3258 <list compact="compact">
3260 <var>new-preinst</var> <tt>install</tt>
3263 <var>new-preinst</var> <tt>install</tt> <var>old-version</var>
3266 <var>new-preinst</var> <tt>upgrade</tt> <var>old-version</var>
3269 <var>old-preinst</var> <tt>abort-upgrade</tt>
3270 <var>new-version</var>
3275 <list compact="compact">
3277 <var>postinst</var> <tt>configure</tt>
3278 <var>most-recently-configured-version</var>
3281 <var>old-postinst</var> <tt>abort-upgrade</tt>
3282 <var>new-version</var>
3285 <var>conflictor's-postinst</var> <tt>abort-remove</tt>
3286 <tt>in-favour</tt> <var>package</var>
3287 <var>new-version</var>
3290 <var>deconfigured's-postinst</var>
3291 <tt>abort-deconfigure</tt> <tt>in-favour</tt>
3292 <var>failed-install-package</var> <var>version</var>
3293 <tt>removing</tt> <var>conflicting-package</var>
3299 <list compact="compact">
3301 <var>prerm</var> <tt>remove</tt>
3304 <var>old-prerm</var> <tt>upgrade</tt>
3305 <var>new-version</var>
3308 <var>new-prerm</var> <tt>failed-upgrade</tt>
3309 <var>old-version</var>
3312 <var>conflictor's-prerm</var> <tt>remove</tt>
3313 <tt>in-favour</tt> <var>package</var>
3314 <var>new-version</var>
3317 <var>deconfigured's-prerm</var> <tt>deconfigure</tt>
3318 <tt>in-favour</tt> <var>package-being-installed</var>
3319 <var>version</var> <tt>removing</tt>
3320 <var>conflicting-package</var>
3326 <list compact="compact">
3328 <var>postrm</var> <tt>remove</tt>
3331 <var>postrm</var> <tt>purge</tt>
3334 <var>old-postrm</var> <tt>upgrade</tt>
3335 <var>new-version</var>
3338 <var>new-postrm</var> <tt>failed-upgrade</tt>
3339 <var>old-version</var>
3342 <var>new-postrm</var> <tt>abort-install</tt>
3345 <var>new-postrm</var> <tt>abort-install</tt>
3346 <var>old-version</var>
3349 <var>new-postrm</var> <tt>abort-upgrade</tt>
3350 <var>old-version</var>
3353 <var>disappearer's-postrm</var> <tt>disappear</tt>
3354 <var>overwriter</var>
3355 <var>overwriter-version</var>
3361 <sect id="unpackphase">
3362 <heading>Details of unpack phase of installation or upgrade</heading>
3365 The procedure on installation/upgrade/overwrite/disappear
3366 (i.e., when running <tt>dpkg --unpack</tt>, or the unpack
3367 stage of <tt>dpkg --install</tt>) is as follows. In each
3368 case, if a major error occurs (unless listed below) the
3369 actions are, in general, run backwards - this means that the
3370 maintainer scripts are run with different arguments in
3371 reverse order. These are the "error unwind" calls listed
3378 If a version of the package is already installed, call
3379 <example compact="compact">
3380 <var>old-prerm</var> upgrade <var>new-version</var>
3384 If the script runs but exits with a non-zero
3385 exit status, <prgn>dpkg</prgn> will attempt:
3386 <example compact="compact">
3387 <var>new-prerm</var> failed-upgrade <var>old-version</var>
3389 Error unwind, for both the above cases:
3390 <example compact="compact">
3391 <var>old-postinst</var> abort-upgrade <var>new-version</var>
3398 If a "conflicting" package is being removed at the same time:
3401 If any packages depended on that conflicting
3402 package and <tt>--auto-deconfigure</tt> is
3403 specified, call, for each such package:
3404 <example compact="compact">
3405 <var>deconfigured's-prerm</var> deconfigure \
3406 in-favour <var>package-being-installed</var> <var>version</var> \
3407 removing <var>conflicting-package</var> <var>version</var>
3410 <example compact="compact">
3411 <var>deconfigured's-postinst</var> abort-deconfigure \
3412 in-favour <var>package-being-installed-but-failed</var> <var>version</var> \
3413 removing <var>conflicting-package</var> <var>version</var>
3415 The deconfigured packages are marked as
3416 requiring configuration, so that if
3417 <tt>--install</tt> is used they will be
3418 configured again if possible.
3421 To prepare for removal of the conflicting package, call:
3422 <example compact="compact">
3423 <var>conflictor's-prerm</var> remove \
3424 in-favour <var>package</var> <var>new-version</var>
3427 <example compact="compact">
3428 <var>conflictor's-postinst</var> abort-remove \
3429 in-favour <var>package</var> <var>new-version</var>
3438 If the package is being upgraded, call:
3439 <example compact="compact">
3440 <var>new-preinst</var> upgrade <var>old-version</var>
3444 Otherwise, if the package had some configuration
3445 files from a previous version installed (i.e., it
3446 is in the "configuration files only" state):
3447 <example compact="compact">
3448 <var>new-preinst</var> install <var>old-version</var>
3452 Otherwise (i.e., the package was completely purged):
3453 <example compact="compact">
3454 <var>new-preinst</var> install
3456 Error unwind actions, respectively:
3457 <example compact="compact">
3458 <var>new-postrm</var> abort-upgrade <var>old-version</var>
3459 <var>new-postrm</var> abort-install <var>old-version</var>
3460 <var>new-postrm</var> abort-install
3468 The new package's files are unpacked, overwriting any
3469 that may be on the system already, for example any
3470 from the old version of the same package or from
3471 another package. Backups of the old files are kept
3472 temporarily, and if anything goes wrong the package
3473 management system will attempt to put them back as
3474 part of the error unwind.
3478 It is an error for a package to contain files which
3479 are on the system in another package, unless
3480 <tt>Replaces</tt> is used (see <ref id="replaces">).
3482 The following paragraph is not currently the case:
3483 Currently the <tt>- - force-overwrite</tt> flag is
3484 enabled, downgrading it to a warning, but this may not
3490 It is a more serious error for a package to contain a
3491 plain file or other kind of non-directory where another
3492 package has a directory (again, unless
3493 <tt>Replaces</tt> is used). This error can be
3494 overridden if desired using
3495 <tt>--force-overwrite-dir</tt>, but this is not
3500 Packages which overwrite each other's files produce
3501 behavior which, though deterministic, is hard for the
3502 system administrator to understand. It can easily
3503 lead to "missing" programs if, for example, a package
3504 is installed which overwrites a file from another
3505 package, and is then removed again.<footnote>
3506 Part of the problem is due to what is arguably a
3507 bug in <prgn>dpkg</prgn>.
3512 A directory will never be replaced by a symbolic link
3513 to a directory or vice versa; instead, the existing
3514 state (symlink or not) will be left alone and
3515 <prgn>dpkg</prgn> will follow the symlink if there is
3524 If the package is being upgraded, call
3525 <example compact="compact">
3526 <var>old-postrm</var> upgrade <var>new-version</var>
3530 If this fails, <prgn>dpkg</prgn> will attempt:
3531 <example compact="compact">
3532 <var>new-postrm</var> failed-upgrade <var>old-version</var>
3534 Error unwind, for both cases:
3535 <example compact="compact">
3536 <var>old-preinst</var> abort-upgrade <var>new-version</var>
3543 This is the point of no return - if
3544 <prgn>dpkg</prgn> gets this far, it won't back off
3545 past this point if an error occurs. This will
3546 leave the package in a fairly bad state, which
3547 will require a successful re-installation to clear
3548 up, but it's when <prgn>dpkg</prgn> starts doing
3549 things that are irreversible.
3554 Any files which were in the old version of the package
3555 but not in the new are removed.
3559 The new file list replaces the old.
3563 The new maintainer scripts replace the old.
3567 Any packages all of whose files have been overwritten
3568 during the installation, and which aren't required for
3569 dependencies, are considered to have been removed.
3570 For each such package
3573 <prgn>dpkg</prgn> calls:
3574 <example compact="compact">
3575 <var>disappearer's-postrm</var> disappear \
3576 <var>overwriter</var> <var>overwriter-version</var>
3580 The package's maintainer scripts are removed.
3583 It is noted in the status database as being in a
3584 sane state, namely not installed (any conffiles
3585 it may have are ignored, rather than being
3586 removed by <prgn>dpkg</prgn>). Note that
3587 disappearing packages do not have their prerm
3588 called, because <prgn>dpkg</prgn> doesn't know
3589 in advance that the package is going to
3596 Any files in the package we're unpacking that are also
3597 listed in the file lists of other packages are removed
3598 from those lists. (This will lobotomize the file list
3599 of the "conflicting" package if there is one.)
3603 The backup files made during installation, above, are
3609 The new package's status is now sane, and recorded as
3614 Here is another point of no return - if the
3615 conflicting package's removal fails we do not unwind
3616 the rest of the installation; the conflicting package
3617 is left in a half-removed limbo.
3622 If there was a conflicting package we go and do the
3623 removal actions (described below), starting with the
3624 removal of the conflicting package's files (any that
3625 are also in the package being installed have already
3626 been removed from the conflicting package's file list,
3627 and so do not get removed now).
3633 <sect id="configdetails"><heading>Details of configuration</heading>
3636 When we configure a package (this happens with <tt>dpkg
3637 --install</tt> and <tt>dpkg --configure</tt>), we first
3638 update any <tt>conffile</tt>s and then call:
3639 <example compact="compact">
3640 <var>postinst</var> configure <var>most-recently-configured-version</var>
3645 No attempt is made to unwind after errors during
3650 If there is no most recently configured version
3651 <prgn>dpkg</prgn> will pass a null argument.
3654 Historical note: Truly ancient (pre-1997) versions of
3655 <prgn>dpkg</prgn> passed <tt><unknown></tt>
3656 (including the angle brackets) in this case. Even older
3657 ones did not pass a second argument at all, under any
3658 circumstance. Note that upgrades using such an old dpkg
3659 version are unlikely to work for other reasons, even if
3660 this old argument behavior is handled by your postinst script.
3666 <sect id="removedetails"><heading>Details of removal and/or
3667 configuration purging</heading>
3672 <example compact="compact">
3673 <var>prerm</var> remove
3677 The package's files are removed (except <tt>conffile</tt>s).
3680 <example compact="compact">
3681 <var>postrm</var> remove
3686 All the maintainer scripts except the <prgn>postrm</prgn>
3691 If we aren't purging the package we stop here. Note
3692 that packages which have no <prgn>postrm</prgn> and no
3693 <tt>conffile</tt>s are automatically purged when
3694 removed, as there is no difference except for the
3695 <prgn>dpkg</prgn> status.
3699 The <tt>conffile</tt>s and any backup files
3700 (<tt>~</tt>-files, <tt>#*#</tt> files,
3701 <tt>%</tt>-files, <tt>.dpkg-{old,new,tmp}</tt>, etc.)
3705 <example compact="compact">
3706 <var>postrm</var> purge
3710 The package's file list is removed.
3714 If there are problems during this process, we call
3715 <example compact="compact">postinst
3716 abort-remove</example>. No other attempt is made to unwind
3717 after errors during removal.
3723 <chapt id="relationships">
3724 <heading>Declaring relationships between packages</heading>
3726 <sect id="depsyntax">
3727 <heading>Syntax of relationship fields</heading>
3730 These fields all have a uniform syntax. They are a list of
3731 package names separated by commas.
3735 In the <tt>Depends</tt>, <tt>Recommends</tt>,
3736 <tt>Suggests</tt>, <tt>Pre-Depends</tt>,
3737 <tt>Build-Depends</tt> and <tt>Build-Depends-Indep</tt>
3738 control file fields of the package, which declare
3739 dependencies on other packages, the package names listed may
3740 also include lists of alternative package names, separated
3741 by vertical bar (pipe) symbols <tt>|</tt>. In such a case,
3742 if any one of the alternative packages is installed, that
3743 part of the dependency is considered to be satisfied.
3747 All of the fields except for <tt>Provides</tt> may restrict
3748 their applicability to particular versions of each named
3749 package. This is done in parentheses after each individual
3750 package name; the parentheses should contain a relation from
3751 the list below followed by a version number, in the format
3752 described in <ref id="f-Version">.
3756 The relations allowed are <tt><<</tt>, <tt><=</tt>,
3757 <tt>=</tt>, <tt>>=</tt> and <tt>>></tt> for
3758 strictly earlier, earlier or equal, exactly equal, later or
3759 equal and strictly later, respectively. The deprecated
3760 forms <tt><</tt> and <tt>></tt> were used to mean
3761 earlier/later or equal, rather than strictly earlier/later,
3762 so they should not appear in new packages (though
3763 <prgn>dpkg</prgn> still supports them).
3767 Whitespace may appear at any point in the version
3768 specification subject to the rules in <ref
3769 id="controlsyntax">, and must appear where it's necessary to
3770 disambiguate; it is not otherwise significant. For
3771 consistency and in case of future changes to
3772 <prgn>dpkg</prgn> it is recommended that a single space be
3773 used after a version relationship and before a version
3774 number; it is also conventional to put a single space after
3775 each comma, on either side of each vertical bar, and before
3776 each open parenthesis.
3780 For example, a list of dependencies might appear as:
3781 <example compact="compact">
3784 Depends: libc6 (>= 2.2.1), exim | mail-transport-agent
3789 All fields that specify build-time relationships
3790 (<tt>Build-Depends</tt>, <tt>Build-Depends-Indep</tt>,
3791 <tt>Build-Conflicts</tt> and <tt>Build-Conflicts-Indep</tt>)
3792 may be restricted to a certain set of architectures. This
3793 is indicated in brackets after each individual package name and
3794 the optional version specification. The brackets enclose a
3795 list of Debian architecture names separated by whitespace.
3796 Exclamation marks may be prepended to each of the names.
3797 (It is not permitted for some names to be prepended with
3798 exclamation marks and others not.) If the current Debian
3799 host architecture is not in this list and there are no
3800 exclamation marks in the list, or it is in the list with a
3801 prepended exclamation mark, the package name and the
3802 associated version specification are ignored completely for
3803 the purposes of defining the relationships.
3808 <example compact="compact">
3810 Build-Depends-Indep: texinfo
3811 Build-Depends: kernel-headers-2.2.10 [!hurd-i386],
3812 hurd-dev [hurd-i386], gnumach-dev [hurd-i386]
3817 Note that the binary package relationship fields such as
3818 <tt>Depends</tt> appear in one of the binary package
3819 sections of the control file, whereas the build-time
3820 relationships such as <tt>Build-Depends</tt> appear in the
3821 source package section of the control file (which is the
3826 <sect id="binarydeps">
3827 <heading>Binary Dependencies - <tt>Depends</tt>,
3828 <tt>Recommends</tt>, <tt>Suggests</tt>, <tt>Enhances</tt>,
3829 <tt>Pre-Depends</tt>
3833 Packages can declare in their control file that they have
3834 certain relationships to other packages - for example, that
3835 they may not be installed at the same time as certain other
3836 packages, and/or that they depend on the presence of others.
3840 This is done using the <tt>Depends</tt>, <tt>Pre-Depends</tt>,
3841 <tt>Recommends</tt>, <tt>Suggests</tt>, <tt>Enhances</tt> and
3842 <tt>Conflicts</tt> control file fields.
3846 These six fields are used to declare a dependency
3847 relationship by one package on another. Except for
3848 <tt>Enhances</tt>, they appear in the depending (binary)
3849 package's control file. (<tt>Enhances</tt> appears in the
3850 recommending package's control file.)
3854 A <tt>Depends</tt> field takes effect <em>only</em> when a
3855 package is to be configured. It does not prevent a package
3856 being on the system in an unconfigured state while its
3857 dependencies are unsatisfied, and it is possible to replace
3858 a package whose dependencies are satisfied and which is
3859 properly installed with a different version whose
3860 dependencies are not and cannot be satisfied; when this is
3861 done the depending package will be left unconfigured (since
3862 attempts to configure it will give errors) and will not
3863 function properly. If it is necessary, a
3864 <tt>Pre-Depends</tt> field can be used, which has a partial
3865 effect even when a package is being unpacked, as explained
3866 in detail below. (The other three dependency fields,
3867 <tt>Recommends</tt>, <tt>Suggests</tt> and
3868 <tt>Enhances</tt>, are only used by the various front-ends
3869 to <prgn>dpkg</prgn> such as <prgn>dselect</prgn>.)
3873 For this reason packages in an installation run are usually
3874 all unpacked first and all configured later; this gives
3875 later versions of packages with dependencies on later
3876 versions of other packages the opportunity to have their
3877 dependencies satisfied.
3881 The <tt>Depends</tt> field thus allows package maintainers
3882 to impose an order in which packages should be configured.
3886 The meaning of the five dependency fields is as follows:
3888 <tag><tt>Depends</tt></tag>
3891 This declares an absolute dependency. A package will
3892 not be configured unless all of the packages listed in
3893 its <tt>Depends</tt> field have been correctly
3898 The <tt>Depends</tt> field should be used if the
3899 depended-on package is required for the depending
3900 package to provide a significant amount of
3905 The <tt>Depends</tt> field should also be used if the
3906 <prgn>postinst</prgn>, <prgn>prerm</prgn> or
3907 <prgn>postrm</prgn> scripts require the package to be
3908 present in order to run. Note, however, that the
3909 <prgn>postrm</prgn> cannot rely on any non-essential
3910 packages to be present during the <tt>purge</tt>
3914 <tag><tt>Recommends</tt></tag>
3917 This declares a strong, but not absolute, dependency.
3921 The <tt>Recommends</tt> field should list packages
3922 that would be found together with this one in all but
3923 unusual installations.
3927 <tag><tt>Suggests</tt></tag>
3929 This is used to declare that one package may be more
3930 useful with one or more others. Using this field
3931 tells the packaging system and the user that the
3932 listed packages are related to this one and can
3933 perhaps enhance its usefulness, but that installing
3934 this one without them is perfectly reasonable.
3937 <tag><tt>Enhances</tt></tag>
3939 This field is similar to Suggests but works in the
3940 opposite direction. It is used to declare that a
3941 package can enhance the functionality of another
3945 <tag><tt>Pre-Depends</tt></tag>
3948 This field is like <tt>Depends</tt>, except that it
3949 also forces <prgn>dpkg</prgn> to complete installation
3950 of the packages named before even starting the
3951 installation of the package which declares the
3952 pre-dependency, as follows:
3956 When a package declaring a pre-dependency is about to
3957 be <em>unpacked</em> the pre-dependency can be
3958 satisfied if the depended-on package is either fully
3959 configured, <em>or even if</em> the depended-on
3960 package(s) are only unpacked or half-configured,
3961 provided that they have been configured correctly at
3962 some point in the past (and not removed or partially
3963 removed since). In this case, both the
3964 previously-configured and currently unpacked or
3965 half-configured versions must satisfy any version
3966 clause in the <tt>Pre-Depends</tt> field.
3970 When the package declaring a pre-dependency is about
3971 to be <em>configured</em>, the pre-dependency will be
3972 treated as a normal <tt>Depends</tt>, that is, it will
3973 be considered satisfied only if the depended-on
3974 package has been correctly configured.
3978 <tt>Pre-Depends</tt> should be used sparingly,
3979 preferably only by packages whose premature upgrade or
3980 installation would hamper the ability of the system to
3981 continue with any upgrade that might be in progress.
3985 <tt>Pre-Depends</tt> are also required if the
3986 <prgn>preinst</prgn> script depends on the named
3987 package. It is best to avoid this situation if
3995 When selecting which level of dependency to use you should
3996 consider how important the depended-on package is to the
3997 functionality of the one declaring the dependency. Some
3998 packages are composed of components of varying degrees of
3999 importance. Such a package should list using
4000 <tt>Depends</tt> the package(s) which are required by the
4001 more important components. The other components'
4002 requirements may be mentioned as Suggestions or
4003 Recommendations, as appropriate to the components' relative
4008 <sect id="conflicts">
4009 <heading>Conflicting binary packages - <tt>Conflicts</tt></heading>
4012 When one binary package declares a conflict with another
4013 using a <tt>Conflicts</tt> field, <prgn>dpkg</prgn> will
4014 refuse to allow them to be installed on the system at the
4019 If one package is to be installed, the other must be removed
4020 first - if the package being installed is marked as
4021 replacing (see <ref id="replaces">) the one on the system,
4022 or the one on the system is marked as deselected, or both
4023 packages are marked <tt>Essential</tt>, then
4024 <prgn>dpkg</prgn> will automatically remove the package
4025 which is causing the conflict, otherwise it will halt the
4026 installation of the new package with an error. This
4027 mechanism is specifically designed to produce an error when
4028 the installed package is <tt>Essential</tt>, but the new
4033 A package will not cause a conflict merely because its
4034 configuration files are still installed; it must be at least
4039 A special exception is made for packages which declare a
4040 conflict with their own package name, or with a virtual
4041 package which they provide (see below): this does not
4042 prevent their installation, and allows a package to conflict
4043 with others providing a replacement for it. You use this
4044 feature when you want the package in question to be the only
4045 package providing some feature.
4049 A <tt>Conflicts</tt> entry should almost never have an
4050 "earlier than" version clause. This would prevent
4051 <prgn>dpkg</prgn> from upgrading or installing the package
4052 which declared such a conflict until the upgrade or removal
4053 of the conflicted-with package had been completed.
4057 <sect id="virtual"><heading>Virtual packages - <tt>Provides</tt>
4061 As well as the names of actual ("concrete") packages, the
4062 package relationship fields <tt>Depends</tt>,
4063 <tt>Recommends</tt>, <tt>Suggests</tt>, <tt>Enhances</tt>,
4064 <tt>Pre-Depends</tt>, <tt>Conflicts</tt>,
4065 <tt>Build-Depends</tt>, <tt>Build-Depends-Indep</tt>,
4066 <tt>Build-Conflicts</tt> and <tt>Build-Conflicts-Indep</tt>
4067 may mention "virtual packages".
4071 A <em>virtual package</em> is one which appears in the
4072 <tt>Provides</tt> control file field of another package.
4073 The effect is as if the package(s) which provide a
4074 particular virtual package name had been listed by name
4075 everywhere the virtual package name appears. (See also <ref
4080 If there are both concrete and virtual packages of the same
4081 name, then the dependency may be satisfied (or the conflict
4082 caused) by either the concrete package with the name in
4083 question or any other concrete package which provides the
4084 virtual package with the name in question. This is so that,
4085 for example, supposing we have
4086 <example compact="compact">
4090 and someone else releases an enhanced version of the
4091 <tt>bar</tt> package (for example, a non-US variant), they
4093 <example compact="compact">
4097 and the <tt>bar-plus</tt> package will now also satisfy the
4098 dependency for the <tt>foo</tt> package.
4102 If a dependency or a conflict has a version number attached
4103 then only real packages will be considered to see whether
4104 the relationship is satisfied (or the prohibition violated,
4105 for a conflict) - it is assumed that a real package which
4106 provides the virtual package is not of the "right" version.
4107 So, a <tt>Provides</tt> field may not contain version
4108 numbers, and the version number of the concrete package
4109 which provides a particular virtual package will not be
4110 looked at when considering a dependency on or conflict with
4111 the virtual package name.
4115 It is likely that the ability will be added in a future
4116 release of <prgn>dpkg</prgn> to specify a version number for
4117 each virtual package it provides. This feature is not yet
4118 present, however, and is expected to be used only
4123 If you want to specify which of a set of real packages
4124 should be the default to satisfy a particular dependency on
4125 a virtual package, you should list the real package as an
4126 alternative before the virtual one.
4131 <sect id="replaces"><heading>Overwriting files and replacing
4132 packages - <tt>Replaces</tt></heading>
4135 Packages can declare in their control file that they should
4136 overwrite files in certain other packages, or completely
4137 replace other packages. The <tt>Replaces</tt> control file
4138 field has these two distinct purposes.
4141 <sect1><heading>Overwriting files in other packages</heading>
4144 Firstly, as mentioned before, it is usually an error for a
4145 package to contain files which are on the system in
4150 However, if the overwriting package declares that it
4151 <tt>Replaces</tt> the one containing the file being
4152 overwritten, then <prgn>dpkg</prgn> will replace the file
4153 from the old package with that from the new. The file
4154 will no longer be listed as "owned" by the old package.
4158 If a package is completely replaced in this way, so that
4159 <prgn>dpkg</prgn> does not know of any files it still
4160 contains, it is considered to have "disappeared". It will
4161 be marked as not wanted on the system (selected for
4162 removal) and not installed. Any <tt>conffile</tt>s
4163 details noted for the package will be ignored, as they
4164 will have been taken over by the overwriting package. The
4165 package's <prgn>postrm</prgn> script will be run with a
4166 special argument to allow the package to do any final
4167 cleanup required. See <ref id="mscriptsinstact">.
4170 Replaces is a one way relationship -- you have to
4171 install the replacing package after the replaced
4178 For this usage of <tt>Replaces</tt>, virtual packages (see
4179 <ref id="virtual">) are not considered when looking at a
4180 <tt>Replaces</tt> field - the packages declared as being
4181 replaced must be mentioned by their real names.
4185 Furthermore, this usage of <tt>Replaces</tt> only takes
4186 effect when both packages are at least partially on the
4187 system at once, so that it can only happen if they do not
4188 conflict or if the conflict has been overridden.
4193 <sect1><heading>Replacing whole packages, forcing their
4197 Secondly, <tt>Replaces</tt> allows the packaging system to
4198 resolve which package should be removed when there is a
4199 conflict - see <ref id="conflicts">. This usage only
4200 takes effect when the two packages <em>do</em> conflict,
4201 so that the two usages of this field do not interfere with
4206 In this situation, the package declared as being replaced
4207 can be a virtual package, so for example, all mail
4208 transport agents (MTAs) would have the following fields in
4209 their control files:
4210 <example compact="compact">
4211 Provides: mail-transport-agent
4212 Conflicts: mail-transport-agent
4213 Replaces: mail-transport-agent
4215 ensuring that only one MTA can be installed at any one
4220 <sect id="sourcebinarydeps">
4221 <heading>Relationships between source and binary packages -
4222 <tt>Build-Depends</tt>, <tt>Build-Depends-Indep</tt>,
4223 <tt>Build-Conflicts</tt>, <tt>Build-Conflicts-Indep</tt>
4227 Source packages that require certain binary packages to be
4228 installed or absent at the time of building the package
4229 can declare relationships to those binary packages.
4233 This is done using the <tt>Build-Depends</tt>,
4234 <tt>Build-Depends-Indep</tt>, <tt>Build-Conflicts</tt> and
4235 <tt>Build-Conflicts-Indep</tt> control file fields.
4239 Build-dependencies on "build-essential" binary packages can be
4240 omitted. Please see <ref id="pkg-relations"> for more information.
4244 The dependencies and conflicts they define must be satisfied
4245 (as defined earlier for binary packages) in order to invoke
4246 the targets in <tt>debian/rules</tt>, as follows:<footnote>
4248 If you make "build-arch" or "binary-arch", you need
4249 Build-Depends. If you make "build-indep" or
4250 "binary-indep", you need Build-Depends and
4251 Build-Depends-Indep. If you make "build" or "binary",
4255 There is no Build-Depends-Arch; the autobuilders will
4256 only need the Build-Depends if they know how to build
4257 only build-arch and binary-arch. Anyone building the
4258 build-indep/binary-indep targets is basically assumed to
4259 be building the whole package and so installs all build
4263 The purpose of the original split, I recall, was so that
4264 the autobuilders wouldn't need to install extra packages
4265 needed only for the binary-indep targets. But without a
4266 build-arch/build-indep split, this didn't work, since
4267 most of the work is done in the build target, not in the
4273 <tag><tt>Build-Depends</tt>, <tt>Build-Conflicts</tt></tag>
4275 The <tt>Build-Depends</tt> and
4276 <tt>Build-Conflicts</tt> fields must be satisfied when
4277 any of the following targets is invoked:
4278 <tt>build</tt>, <tt>clean</tt>, <tt>binary</tt>,
4279 <tt>binary-arch</tt>, <tt>build-arch</tt>,
4280 <tt>build-indep</tt> and <tt>binary-indep</tt>.
4282 <tag><tt>Build-Depends-Indep</tt>,
4283 <tt>Build-Conflicts-Indep</tt></tag>
4285 The <tt>Build-Depends-Indep</tt> and
4286 <tt>Build-Conflicts-Indep</tt> fields must be
4287 satisfied when any of the following targets is
4288 invoked: <tt>build</tt>, <tt>build-indep</tt>,
4289 <tt>binary</tt> and <tt>binary-indep</tt>.
4299 <chapt id="sharedlibs"><heading>Shared libraries</heading>
4302 Packages containing shared libraries must be constructed with
4303 a little care to make sure that the shared library is always
4304 available. This is especially important for packages whose
4305 shared libraries are vitally important, such as the C library
4306 (currently <tt>libc6</tt>).
4310 Packages involving shared libraries should be split up into
4311 several binary packages. This section mostly deals with how
4312 this separation is to be accomplished; rules for files within
4313 the shared library packages are in <ref id="libraries"> instead.
4316 <sect id="sharedlibs-runtime">
4317 <heading>Run-time shared libraries</heading>
4320 The run-time shared library needs to be placed in a package called
4321 <package><var>libraryname</var><var>soversion</var></package>, where
4322 <file><var>soversion</var></file> is the version number in the
4323 soname of the shared library<footnote>
4324 The soname is the shared object name: it's the thing
4325 that has to match exactly between building an executable
4326 and running it for the dynamic linker to be able run the
4327 program. For example, if the soname of the library is
4328 <file>libfoo.so.6</file>, the library package would be
4329 called <file>libfoo6</file>.
4331 Alternatively, if it would be confusing to directly append
4332 <var>soversion</var> to <var>libraryname</var> (e.g. because
4333 <var>libraryname</var> itself ends in a number), you may use
4334 <package><var>libraryname</var>-<var>soversion</var></package> and
4335 <package><var>libraryname</var>-<var>soversion</var>-dev</package>
4340 If you have several shared libraries built from the same
4341 source tree you may lump them all together into a single
4342 shared library package, provided that you change all of
4343 their sonames at once (so that you don't get filename
4344 clashes if you try to install different versions of the
4345 combined shared libraries package).
4349 The package should install the shared libraries under
4350 their normal names. For example, the <package>libgdbm3</package>
4351 package should install <file>libgdbm.so.3.0.0</file> as
4352 <file>/usr/lib/libgdbm.so.3.0.0</file>. The files should not be
4353 renamed or re-linked by any <prgn>prerm</prgn> or
4354 <prgn>postrm</prgn> scripts; <prgn>dpkg</prgn> will take care
4355 of renaming things safely without affecting running programs,
4356 and attempts to interfere with this are likely to lead to
4361 Shared libraries should not be installed executable, since
4362 the dynamic linker does not require this and trying to
4363 execute a shared library usually results in a core dump.
4367 The run-time library package should include the symbolic link that
4368 <prgn>ldconfig</prgn> would create for the shared libraries.
4369 For example, the <package>libgdbm3</package> package should include
4370 a symbolic link from <file>/usr/lib/libgdbm.so.3</file> to
4371 <file>libgdbm.so.3.0.0</file>. This is needed so that the dynamic
4372 linker (for example <prgn>ld.so</prgn> or
4373 <prgn>ld-linux.so.*</prgn>) can find the library between the
4374 time that <prgn>dpkg</prgn> installs it and the time that
4375 <prgn>ldconfig</prgn> is run in the <prgn>postinst</prgn>
4377 The package management system requires the library to be
4378 placed before the symbolic link pointing to it in the
4379 <file>.deb</file> file. This is so that when
4380 <prgn>dpkg</prgn> comes to install the symlink
4381 (overwriting the previous symlink pointing at an older
4382 version of the library), the new shared library is already
4383 in place. In the past, this was achieved by creating the
4384 library in the temporary packaging directory before
4385 creating the symlink. Unfortunately, this was not always
4386 effective, since the building of the tar file in the
4387 <file>.deb</file> depended on the behavior of the underlying
4388 file system. Some file systems (such as reiserfs) reorder
4389 the files so that the order of creation is forgotten.
4390 Since version 1.7.0, <prgn>dpkg</prgn>
4391 reorders the files itself as necessary when building a
4392 package. Thus it is no longer important to concern
4393 oneself with the order of file creation.
4397 <sect1 id="ldconfig">
4398 <heading><tt>ldconfig</tt></heading>
4401 Any package installing shared libraries in one of the default
4402 library directories of the dynamic linker (which are currently
4403 <file>/usr/lib</file> and <file>/lib</file>) or a directory that is
4404 listed in <file>/etc/ld.so.conf</file><footnote>
4406 <list compact="compact">
4407 <item>/usr/X11R6/lib/Xaw3d</item>
4408 <item>/usr/local/lib</item>
4409 <item>/usr/lib/libc5-compat</item>
4410 <item>/lib/libc5-compat</item>
4411 <item>/usr/X11R6/lib</item>
4414 must use <prgn>ldconfig</prgn> to update the shared library
4419 The package must call <prgn>ldconfig</prgn> in the
4420 <prgn>postinst</prgn> script if the first argument is
4421 <tt>configure</tt>; the <prgn>postinst</prgn> script may
4422 optionally invoke <prgn>ldconfig</prgn> at other times. The
4423 package should call <prgn>ldconfig</prgn> in the
4424 <prgn>postrm</prgn> script if the first argument is
4425 <tt>remove</tt>. The maintainer scripts must not invoke
4426 <prgn>ldconfig</prgn> under any circumstances other than those
4427 described in this paragraph.<footnote>
4429 During install or upgrade, the preinst is called before
4430 the new files are installed, so calling "ldconfig" is
4431 pointless. The preinst of an existing package can also be
4432 called if an upgrade fails. However, this happens during
4433 the critical time when a shared libs may exist on-disk
4434 under a temporary name. Thus, it is dangerous and
4435 forbidden by current policy to call "ldconfig" at this
4440 When a package is installed or upgraded, "postinst
4441 configure" runs after the new files are safely on-disk.
4442 Since it is perfectly safe to invoke ldconfig
4443 unconditionally in a postinst, it is OK for a package to
4444 simply put ldconfig in its postinst without checking the
4445 argument. The postinst can also be called to recover from
4446 a failed upgrade. This happens before any new files are
4447 unpacked, so there is no reason to call "ldconfig" at this
4452 For a package that is being removed, prerm is
4453 called with all the files intact, so calling ldconfig is
4454 useless. The other calls to "prerm" happen in the case of
4455 upgrade at a time when all the files of the old package
4456 are on-disk, so again calling "ldconfig" is pointless.
4460 postrm, on the other hand, is called with the "remove"
4461 argument just after the files are removed, so this is the
4462 proper time to call "ldconfig" to notify the system of the
4463 fact shared libraries from the package are removed.
4464 The postrm can be called at several other times. At the
4465 time of "postrm purge", "postrm abort-install", or "postrm
4466 abort-upgrade", calling "ldconfig" is useless because the
4467 shared lib files are not on-disk. However, when "postrm"
4468 is invoked with arguments "upgrade", "failed-upgrade", or
4469 "disappear", a shared lib may exist on-disk under a
4478 <sect id="sharedlibs-runtime-progs">
4479 <heading>Run-time support programs</heading>
4482 If your package has some run-time support programs which use
4483 the shared library you must not put them in the shared
4484 library package. If you do that then you won't be able to
4485 install several versions of the shared library without
4486 getting filename clashes.
4490 Instead, either create another package for the runtime binaries
4491 (this package might typically be named
4492 <package><var>libraryname</var>-runtime</package>; note the absence
4493 of the <var>soversion</var> in the package name), or if the
4494 development package is small, include them in there.
4498 <sect id="sharedlibs-static">
4499 <heading>Static libraries</heading>
4502 The static library (<file><var>libraryname.a</var></file>)
4503 is usually provided in addition to the shared version.
4504 It is placed into the development package (see below).
4508 In some cases, it is acceptable for a library to be
4509 available in static form only; these cases include:
4511 <item>libraries for languages whose shared library support
4512 is immature or unstable</item>
4513 <item>libraries whose interfaces are in flux or under
4514 development (commonly the case when the library's
4515 major version number is zero, or where the ABI breaks
4516 across patchlevels)</item>
4517 <item>libraries which are explicitly intended to be
4518 available only in static form by their upstream
4523 <sect id="sharedlibs-dev">
4524 <heading>Development files</heading>
4527 The development files associated to a shared library need to be
4528 placed in a package called
4529 <package><var>libraryname</var><var>soversion</var>-dev</package>,
4530 or if you prefer only to support one development version at a
4531 time, <package><var>libraryname</var>-dev</package>.
4535 In case several development versions of a library exist, you may
4536 need to use <prgn>dpkg</prgn>'s Conflicts mechanism (see
4537 <ref id="conflicts">) to ensure that the user only installs one
4538 development version at a time (as different development versions are
4539 likely to have the same header files in them, which would cause a
4540 filename clash if both were installed).
4544 The development package should contain a symlink for the associated
4545 shared library without a version number. For example, the
4546 <package>libgdbm-dev</package> package should include a symlink
4547 from <file>/usr/lib/libgdbm.so</file> to
4548 <file>libgdbm.so.3.0.0</file>. This symlink is needed by the linker
4549 (<prgn>ld</prgn>) when compiling packages, as it will only look for
4550 <file>libgdbm.so</file> when compiling dynamically.
4554 <sect id="sharedlibs-intradeps">
4555 <heading>Dependencies between the packages of the same library</heading>
4558 Typically the development version should have an exact
4559 version dependency on the runtime library, to make sure that
4560 compilation and linking happens correctly. The
4561 <tt>${Source-Version}</tt> substitution variable can be
4562 useful for this purpose.
4566 <sect id="sharedlibs-shlibdeps">
4567 <heading>Dependencies between the library and other packages -
4568 the <tt>shlibs</tt> system</heading>
4571 If a package contains a binary or library which links to a
4572 shared library, we must ensure that when the package is
4573 installed on the system, all of the libraries needed are
4574 also installed. This requirement led to the creation of the
4575 <tt>shlibs</tt> system, which is very simple in its design:
4576 any package which <em>provides</em> a shared library also
4577 provides information on the package dependencies required to
4578 ensure the presence of this library, and any package which
4579 <em>uses</em> a shared library uses this information to
4580 determine the dependencies it requires. The files which
4581 contain the mapping from shared libraries to the necessary
4582 dependency information are called <file>shlibs</file> files.
4586 Thus, when a package is built which contains any shared
4587 libraries, it must provide a <file>shlibs</file> file for other
4588 packages to use, and when a package is built which contains
4589 any shared libraries or compiled binaries, it must run
4590 <prgn>dpkg-shlibdeps</prgn> on these to determine the
4591 libraries used and hence the dependencies needed by this
4594 In the past, the shared libraries linked to were
4595 determined by calling <prgn>ldd</prgn>, but now
4596 <prgn>objdump</prgn> is used to do this. The only
4597 change this makes to package building is that
4598 <prgn>dpkg-shlibdeps</prgn> must also be run on shared
4599 libraries, whereas in the past this was unnecessary.
4600 The rest of this footnote explains the advantage that
4605 We say that a binary <tt>foo</tt> <em>directly</em> uses
4606 a library <tt>libbar</tt> if it is explicitly linked
4607 with that library (that is, it uses the flag
4608 <tt>-lbar</tt> during the linking stage). Other
4609 libraries that are needed by <tt>libbar</tt> are linked
4610 <em>indirectly</em> to <tt>foo</tt>, and the dynamic
4611 linker will load them automatically when it loads
4612 <tt>libbar</tt>. A package should depend on
4613 the libraries it directly uses, and the dependencies for
4614 those libraries should automatically pull in the other
4619 Unfortunately, the <prgn>ldd</prgn> program shows both
4620 the directly and indirectly used libraries, meaning that
4621 the dependencies determined included both direct and
4622 indirect dependencies. The use of <prgn>objdump</prgn>
4623 avoids this problem by determining only the directly
4628 A good example of where this helps is the following. We
4629 could update <tt>libimlib</tt> with a new version that
4630 supports a new graphics format called dgf (but retaining
4631 the same major version number). If we used the old
4632 <prgn>ldd</prgn> method, every package that uses
4633 <tt>libimlib</tt> would need to be recompiled so it
4634 would also depend on <tt>libdgf</tt> or it wouldn't run
4635 due to missing symbols. However with the new system,
4636 packages using <tt>libimlib</tt> can rely on
4637 <tt>libimlib</tt> itself having the dependency on
4638 <tt>libdgf</tt> and so they would not need rebuilding.
4644 In the following sections, we will first describe where the
4645 various <tt>shlibs</tt> files are to be found, then how to
4646 use <prgn>dpkg-shlibdeps</prgn>, and finally the
4647 <tt>shlibs</tt> file format and how to create them if your
4648 package contains a shared library.
4652 <heading>The <tt>shlibs</tt> files present on the system</heading>
4655 There are several places where <tt>shlibs</tt> files are
4656 found. The following list gives them in the order in which
4657 they are read by <prgn>dpkg-shlibdeps</prgn>. (The first
4658 one which gives the required information is used.)
4664 <p><file>debian/shlibs.local</file></p>
4667 This lists overrides for this package. Its use is
4668 described below (see <ref id="shlibslocal">).
4673 <p><file>/etc/dpkg/shlibs.override</file></p>
4676 This lists global overrides. This list is normally
4677 empty. It is maintained by the local system
4683 <p><file>DEBIAN/shlibs</file> files in the "build directory"</p>
4686 When packages are being built, any
4687 <file>debian/shlibs</file> files are copied into the
4688 control file area of the temporary build directory and
4689 given the name <file>shlibs</file>. These files give
4690 details of any shared libraries included in the
4692 An example may help here. Let us say that the
4693 source package <tt>foo</tt> generates two binary
4694 packages, <tt>libfoo2</tt> and
4695 <tt>foo-runtime</tt>. When building the binary
4696 packages, the two packages are created in the
4697 directories <file>debian/libfoo2</file> and
4698 <file>debian/foo-runtime</file> respectively.
4699 (<file>debian/tmp</file> could be used instead of one
4700 of these.) Since <tt>libfoo2</tt> provides the
4701 <tt>libfoo</tt> shared library, it will require a
4702 <tt>shlibs</tt> file, which will be installed in
4703 <file>debian/libfoo2/DEBIAN/shlibs</file>, eventually
4705 <file>/var/lib/dpkg/info/libfoo2.shlibs</file>. Then
4706 when <prgn>dpkg-shlibdeps</prgn> is run on the
4708 <file>debian/foo-runtime/usr/bin/foo-prog</file>, it
4710 <file>debian/libfoo2/DEBIAN/shlibs</file> file to
4711 determine whether <tt>foo-prog</tt>'s library
4712 dependencies are satisfied by any of the libraries
4713 provided by <tt>libfoo2</tt>. For this reason,
4714 <prgn>dpkg-shlibdeps</prgn> must only be run once
4715 all of the individual binary packages'
4716 <tt>shlibs</tt> files have been installed into the
4723 <p><file>/var/lib/dpkg/info/*.shlibs</file></p>
4726 These are the <file>shlibs</file> files corresponding to
4727 all of the packages installed on the system, and are
4728 maintained by the relevant package maintainers.
4733 <p><file>/etc/dpkg/shlibs.default</file></p>
4736 This file lists any shared libraries whose packages
4737 have failed to provide correct <file>shlibs</file> files.
4738 It was used when the <file>shlibs</file> setup was first
4739 introduced, but it is now normally empty. It is
4740 maintained by the <tt>dpkg</tt> maintainer.
4748 <heading>How to use <prgn>dpkg-shlibdeps</prgn> and the
4749 <file>shlibs</file> files</heading>
4752 Put a call to <prgn>dpkg-shlibdeps</prgn> into your
4753 <file>debian/rules</file> file. If your package contains only
4754 compiled binaries and libraries (but no scripts), you can
4755 use a command such as:
4756 <example compact="compact">
4757 dpkg-shlibdeps debian/tmp/usr/bin/* debian/tmp/usr/sbin/* \
4758 debian/tmp/usr/lib/*
4760 Otherwise, you will need to explicitly list the compiled
4761 binaries and libraries.<footnote>
4762 If you are using <tt>debhelper</tt>, the
4763 <prgn>dh_shlibdeps</prgn> program will do this work for
4764 you. It will also correctly handle multi-binary
4770 This command puts the dependency information into the
4771 <file>debian/substvars</file> file, which is then used by
4772 <prgn>dpkg-gencontrol</prgn>. You will need to place a
4773 <tt>${shlib:Depends}</tt> variable in the <tt>Depends</tt>
4774 field in the control file for this to work.
4778 If <prgn>dpkg-shlibdeps</prgn> doesn't complain, you're
4779 done. If it does complain you might need to create your own
4780 <file>debian/shlibs.local</file> file, as explained below (see
4781 <ref id="shlibslocal">).
4785 If you have multiple binary packages, you will need to call
4786 <prgn>dpkg-shlibdeps</prgn> on each one which contains
4787 compiled libraries or binaries. In such a case, you will
4788 need to use the <tt>-T</tt> option to the <tt>dpkg</tt>
4789 utilities to specify a different <file>substvars</file> file.
4790 For more details on this and other options, see <manref
4791 name="dpkg-shlibdeps" section="1">.
4796 <heading>The <file>shlibs</file> File Format</heading>
4799 Each <file>shlibs</file> file has the same format. Lines
4800 beginning with <tt>#</tt> are considered to be comments and
4801 are ignored. Each line is of the form:
4802 <example compact="compact">
4803 <var>library-name</var> <var>soname-version-number</var> <var>dependencies ...</var>
4808 We will explain this by reference to the example of the
4809 <tt>zlib1g</tt> package, which (at the time of writing)
4810 installs the shared library <file>/usr/lib/libz.so.1.1.3</file>.
4814 <var>library-name</var> is the name of the shared library,
4815 in this case <tt>libz</tt>. (This must match the name part
4816 of the soname, see below.)
4820 <var>soname-version-number</var> is the version part of the
4821 soname of the library. The soname is the thing that must
4822 exactly match for the library to be recognized by the
4823 dynamic linker, and is usually of the form
4824 <tt><var>name</var>.so.<var>major-version</var></tt>, in our
4825 example, <tt>libz.so.1</tt>.<footnote>
4826 This can be determined using the command
4827 <example compact="compact">
4828 objdump -p /usr/lib/libz.so.1.1.3 | grep SONAME
4831 The version part is the part which comes after
4832 <tt>.so.</tt>, so in our case, it is <tt>1</tt>.
4836 <var>dependencies</var> has the same syntax as a dependency
4837 field in a binary package control file. It should give
4838 details of which packages are required to satisfy a binary
4839 built against the version of the library contained in the
4840 package. See <ref id="depsyntax"> for details.
4844 In our example, if the first version of the <tt>zlib1g</tt>
4845 package which contained a minor number of at least
4846 <tt>1.3</tt> was <var>1:1.1.3-1</var>, then the
4847 <tt>shlibs</tt> entry for this library could say:
4848 <example compact="compact">
4849 libz 1 zlib1g (>= 1:1.1.3)
4851 The version-specific dependency is to avoid warnings from
4852 the dynamic linker about using older shared libraries with
4858 <heading>Providing a <file>shlibs</file> file</heading>
4861 If your package provides a shared library, you should create
4862 a <file>shlibs</file> file following the format described above.
4863 It is usual to call this file <file>debian/shlibs</file> (but if
4864 you have multiple binary packages, you might want to call it
4865 <file>debian/shlibs.<var>package</var></file> instead). Then
4866 let <file>debian/rules</file> install it in the control area:
4867 <example compact="compact">
4868 install -m644 debian/shlibs debian/tmp/DEBIAN
4870 or, in the case of a multi-binary package:
4871 <example compact="compact">
4872 install -m644 debian/shlibs.<var>package</var> debian/<var>package</var>/DEBIAN/shlibs
4874 An alternative way of doing this is to create the
4875 <file>shlibs</file> file in the control area directly from
4876 <file>debian/rules</file> without using a <file>debian/shlibs</file>
4877 file at all,<footnote>
4878 This is what <prgn>dh_makeshlibs</prgn> in the
4879 <tt>debhelper</tt> suite does.
4881 since the <file>debian/shlibs</file> file itself is ignored by
4882 <prgn>dpkg-shlibdeps</prgn>.
4886 As <prgn>dpkg-shlibdeps</prgn> reads the
4887 <file>DEBIAN/shlibs</file> files in all of the binary packages
4888 being built from this source package, all of the
4889 <file>DEBIAN/shlibs</file> files should be installed before
4890 <prgn>dpkg-shlibdeps</prgn> is called on any of the binary
4895 <sect1 id="shlibslocal">
4896 <heading>Writing the <file>debian/shlibs.local</file> file</heading>
4899 This file is intended only as a <em>temporary</em> fix if
4900 your binaries or libraries depend on a library whose package
4901 does not yet provide a correct <file>shlibs</file> file.
4905 We will assume that you are trying to package a binary
4906 <tt>foo</tt>. When you try running
4907 <prgn>dpkg-shlibdeps</prgn> you get the following error
4908 message (<tt>-O</tt> displays the dependency information on
4909 <tt>stdout</tt> instead of writing it to
4910 <tt>debian/substvars</tt>, and the lines have been wrapped
4911 for ease of reading):
4912 <example compact="compact">
4913 $ dpkg-shlibdeps -O debian/tmp/usr/bin/foo
4914 dpkg-shlibdeps: warning: unable to find dependency
4915 information for shared library libbar (soname 1,
4916 path /usr/lib/libbar.so.1, dependency field Depends)
4917 shlibs:Depends=libc6 (>= 2.2.2-2)
4919 You can then run <prgn>ldd</prgn> on the binary to find the
4920 full location of the library concerned:
4921 <example compact="compact">
4923 libbar.so.1 => /usr/lib/libbar.so.1 (0x4001e000)
4924 libc.so.6 => /lib/libc.so.6 (0x40032000)
4925 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
4927 So the <prgn>foo</prgn> binary depends on the
4928 <prgn>libbar</prgn> shared library, but no package seems to
4929 provide a <file>*.shlibs</file> file handling
4930 <file>libbar.so.1</file> in <file>/var/lib/dpkg/info/</file>. Let's
4931 determine the package responsible:
4932 <example compact="compact">
4933 $ dpkg -S /usr/lib/libbar.so.1
4934 bar1: /usr/lib/libbar.so.1
4935 $ dpkg -s bar1 | grep Version
4938 This tells us that the <tt>bar1</tt> package, version 1.0-1,
4939 is the one we are using. Now we can file a bug against the
4940 <tt>bar1</tt> package and create our own
4941 <file>debian/shlibs.local</file> to locally fix the problem.
4942 Including the following line into your
4943 <file>debian/shlibs.local</file> file:
4944 <example compact="compact">
4945 libbar 1 bar1 (>= 1.0-1)
4947 should allow the package build to work.
4951 As soon as the maintainer of <tt>bar1</tt> provides a
4952 correct <file>shlibs</file> file, you should remove this line
4953 from your <file>debian/shlibs.local</file> file. (You should
4954 probably also then have a versioned <tt>Build-Depends</tt>
4955 on <tt>bar1</tt> to help ensure that others do not have the
4956 same problem building your package.)
4965 <chapt id="opersys"><heading>The Operating System</heading>
4968 <heading>Filesystem hierarchy</heading>
4972 <heading>Filesystem Structure</heading>
4975 The location of all installed files and directories must
4976 comply with the Filesystem Hierarchy Standard (FHS),
4977 version 2.1, except where doing so would violate other
4978 terms of Debian Policy. The version of this document
4979 referred here can be found in the <tt>debian-policy</tt>
4981 <url id="http://www.debian.org/doc/packaging-manuals/fhs/"
4982 name="FHS (Debian copy)"> alongside this manual (or, if
4983 you have the <package>debian-policy</package> installed,
4985 id="file:///usr/share/doc/debian-policy/fhs/" name="FHS
4986 (local copy)">). The
4987 latest version, which may be a more recent version, may
4989 <url id="http://www.pathname.com/fhs/" name="FHS (upstream)">.
4990 Specific questions about following the standard may be
4991 asked on the <tt>debian-devel</tt> mailing list, or
4992 referred to the FHS mailing list (see the
4993 <url id="http://www.pathname.com/fhs/" name="FHS web site"> for
4999 <heading>Site-specific programs</heading>
5002 As mandated by the FHS, packages must not place any
5003 files in <file>/usr/local</file>, either by putting them in
5004 the file system archive to be unpacked by <prgn>dpkg</prgn>
5005 or by manipulating them in their maintainer scripts.
5009 However, the package may create empty directories below
5010 <file>/usr/local</file> so that the system administrator knows
5011 where to place site-specific files. These directories
5012 should be removed on package removal if they are
5017 Note, that this applies only to directories <em>below</em>
5018 <file>/usr/local</file>, not <em>in</em> <file>/usr/local</file>.
5019 Packages must not create sub-directories in the directory
5020 <file>/usr/local</file> itself, except those listed in FHS,
5021 section 4.5. However, you may create directories below
5022 them as you wish. You must not remove any of the
5023 directories listed in 4.5, even if you created them.
5027 Since <file>/usr/local</file> can be mounted read-only from a
5028 remote server, these directories must be created and
5029 removed by the <prgn>postinst</prgn> and <prgn>prerm</prgn>
5030 maintainer scripts and not be included in the
5031 <file>.deb</file> archive. These scripts must not fail if
5032 either of these operations fail.
5036 For example, the <tt>emacsen-common</tt> package could
5037 contain something like
5038 <example compact="compact">
5039 if [ ! -e /usr/local/share/emacs ]
5041 if mkdir /usr/local/share/emacs 2>/dev/null
5043 chown root:staff /usr/local/share/emacs
5044 chmod 2775 /usr/local/share/emacs
5048 in its <prgn>postinst</prgn> script, and
5049 <example compact="compact">
5050 rmdir /usr/local/share/emacs/site-lisp 2>/dev/null || true
5051 rmdir /usr/local/share/emacs 2>/dev/null || true
5053 in the <prgn>prerm</prgn> script. (Note that this form is
5054 used to ensure that if the script is interrupted, the
5055 directory <file>/usr/local/share/emacs</file> will still be
5060 If you do create a directory in <file>/usr/local</file> for
5061 local additions to a package, you should ensure that
5062 settings in <file>/usr/local</file> take precedence over the
5063 equivalents in <file>/usr</file>.
5067 However, because <file>/usr/local</file> and its contents are
5068 for exclusive use of the local administrator, a package
5069 must not rely on the presence or absence of files or
5070 directories in <file>/usr/local</file> for normal operation.
5074 The <file>/usr/local</file> directory itself and all the
5075 subdirectories created by the package should (by default) have
5076 permissions 2775 (group-writable and set-group-id) and be
5077 owned by <tt>root.staff</tt>.
5082 <heading>The system-wide mail directory</heading>
5084 The system-wide mail directory is <file>/var/mail</file>. This
5085 directory is part of the base system and should not owned
5086 by any particular mail agents. The use of the old
5087 location <file>/var/spool/mail</file> is deprecated, even
5088 though the spool may still be physically located there.
5089 To maintain partial upgrade compatibility for systems
5090 which have <file>/var/spool/mail</file> as their physical mail
5091 spool, packages using <file>/var/mail</file> must depend on
5092 either <package>libc6</package> (>= 2.1.3-13), or on
5093 <package>base-files</package> (>= 2.2.0), or on later
5094 versions of either one of these packages.
5100 <heading>Users and groups</heading>
5103 <heading>Introduction</heading>
5105 The Debian system can be configured to use either plain or
5110 Some user ids (UIDs) and group ids (GIDs) are reserved
5111 globally for use by certain packages. Because some
5112 packages need to include files which are owned by these
5113 users or groups, or need the ids compiled into binaries,
5114 these ids must be used on any Debian system only for the
5115 purpose for which they are allocated. This is a serious
5116 restriction, and we should avoid getting in the way of
5117 local administration policies. In particular, many sites
5118 allocate users and/or local system groups starting at 100.
5122 Apart from this we should have dynamically allocated ids,
5123 which should by default be arranged in some sensible
5124 order, but the behavior should be configurable.
5128 Packages other than <tt>base-passwd</tt> must not modify
5129 <file>/etc/passwd</file>, <file>/etc/shadow</file>,
5130 <file>/etc/group</file> or <file>/etc/gshadow</file>.
5135 <heading>UID and GID classes</heading>
5137 The UID and GID numbers are divided into classes as
5143 Globally allocated by the Debian project, the same
5144 on every Debian system. These ids will appear in
5145 the <file>passwd</file> and <file>group</file> files of all
5146 Debian systems, new ids in this range being added
5147 automatically as the <tt>base-passwd</tt> package is
5152 Packages which need a single statically allocated
5153 uid or gid should use one of these; their
5154 maintainers should ask the <tt>base-passwd</tt>
5162 Dynamically allocated system users and groups.
5163 Packages which need a user or group, but can have
5164 this user or group allocated dynamically and
5165 differently on each system, should use <tt>adduser
5166 --system</tt> to create the group and/or user.
5167 <prgn>adduser</prgn> will check for the existence of
5168 the user or group, and if necessary choose an unused
5169 id based on the ranges specified in
5170 <file>adduser.conf</file>.
5174 <tag>1000-29999:</tag>
5177 Dynamically allocated user accounts. By default
5178 <prgn>adduser</prgn> will choose UIDs and GIDs for
5179 user accounts in this range, though
5180 <file>adduser.conf</file> may be used to modify this
5185 <tag>30000-59999:</tag>
5190 <tag>60000-64999:</tag>
5193 Globally allocated by the Debian project, but only
5194 created on demand. The ids are allocated centrally
5195 and statically, but the actual accounts are only
5196 created on users' systems on demand.
5200 These ids are for packages which are obscure or
5201 which require many statically-allocated ids. These
5202 packages should check for and create the accounts in
5203 <file>/etc/passwd</file> or <file>/etc/group</file> (using
5204 <prgn>adduser</prgn> if it has this facility) if
5205 necessary. Packages which are likely to require
5206 further allocations should have a "hole" left after
5207 them in the allocation, to give them room to
5212 <tag>65000-65533:</tag>
5220 User <tt>nobody</tt>. The corresponding gid refers
5221 to the group <tt>nogroup</tt>.
5228 <tt>(uid_t)(-1) == (gid_t)(-1)</tt> <em>must
5229 not</em> be used, because it is the error return
5238 <sect id="sysvinit">
5239 <heading>System run levels and <file>init.d</file> scripts</heading>
5241 <sect1 id="/etc/init.d">
5242 <heading>Introduction</heading>
5245 The <file>/etc/init.d</file> directory contains the scripts
5246 executed by <prgn>init</prgn> at boot time and when the
5247 init state (or "runlevel") is changed (see <manref
5248 name="init" section="8">).
5252 There are at least two different, yet functionally
5253 equivalent, ways of handling these scripts. For the sake
5254 of simplicity, this document describes only the symbolic
5255 link method. However, it must not be assumed by maintainer
5256 scripts that this method is being used, and any automated
5257 manipulation of the various runlevel behaviours by
5258 maintainer scripts must be performed using
5259 <prgn>update-rc.d</prgn> as described below and not by
5260 manually installing or removing symlinks. For information
5261 on the implementation details of the other method,
5262 implemented in the <tt>file-rc</tt> package, please refer
5263 to the documentation of that package.
5267 These scripts are referenced by symbolic links in the
5268 <file>/etc/rc<var>n</var>.d</file> directories. When changing
5269 runlevels, <prgn>init</prgn> looks in the directory
5270 <file>/etc/rc<var>n</var>.d</file> for the scripts it should
5271 execute, where <tt><var>n</var></tt> is the runlevel that
5272 is being changed to, or <tt>S</tt> for the boot-up
5277 The names of the links all have the form
5278 <file>S<var>mm</var><var>script</var></file> or
5279 <file>K<var>mm</var><var>script</var></file> where
5280 <var>mm</var> is a two-digit number and <var>script</var>
5281 is the name of the script (this should be the same as the
5282 name of the actual script in <file>/etc/init.d</file>).
5286 When <prgn>init</prgn> changes runlevel first the targets
5287 of the links whose names start with a <tt>K</tt> are
5288 executed, each with the single argument <tt>stop</tt>,
5289 followed by the scripts prefixed with an <tt>S</tt>, each
5290 with the single argument <tt>start</tt>. (The links are
5291 those in the <file>/etc/rc<var>n</var>.d</file> directory
5292 corresponding to the new runlevel.) The <tt>K</tt> links
5293 are responsible for killing services and the <tt>S</tt>
5294 link for starting services upon entering the runlevel.
5298 For example, if we are changing from runlevel 2 to
5299 runlevel 3, init will first execute all of the <tt>K</tt>
5300 prefixed scripts it finds in <file>/etc/rc3.d</file>, and then
5301 all of the <tt>S</tt> prefixed scripts in that directory.
5302 The links starting with <tt>K</tt> will cause the
5303 referred-to file to be executed with an argument of
5304 <tt>stop</tt>, and the <tt>S</tt> links with an argument
5309 The two-digit number <var>mm</var> is used to determine
5310 the order in which to run the scripts: low-numbered links
5311 have their scripts run first. For example, the
5312 <tt>K20</tt> scripts will be executed before the
5313 <tt>K30</tt> scripts. This is used when a certain service
5314 must be started before another. For example, the name
5315 server <prgn>bind</prgn> might need to be started before
5316 the news server <prgn>inn</prgn> so that <prgn>inn</prgn>
5317 can set up its access lists. In this case, the script
5318 that starts <prgn>bind</prgn> would have a lower number
5319 than the script that starts <prgn>inn</prgn> so that it
5321 <example compact="compact">
5328 The two runlevels 0 (halt) and 6 (reboot) are slightly
5329 different. In these runlevels, the links with an
5330 <tt>S</tt> prefix are still called after those with a
5331 <tt>K</tt> prefix, but they too are called with the single
5332 argument <tt>stop</tt>.
5336 Also, if the script name ends <tt>.sh</tt>, the script
5337 will be sourced in runlevel <tt>S</tt> rather that being
5338 run in a forked subprocess, but will be explicitly run by
5339 <prgn>sh</prgn> in all other runlevels.
5344 <heading>Writing the scripts</heading>
5347 Packages that include daemons for system services should
5348 place scripts in <file>/etc/init.d</file> to start or stop
5349 services at boot time or during a change of runlevel.
5350 These scripts should be named
5351 <file>/etc/init.d/<var>package</var></file>, and they should
5352 accept one argument, saying what to do:
5355 <tag><tt>start</tt></tag>
5356 <item>start the service,</item>
5358 <tag><tt>stop</tt></tag>
5359 <item>stop the service,</item>
5361 <tag><tt>restart</tt></tag>
5362 <item>stop and restart the service if it's already running,
5363 otherwise start the service</item>
5365 <tag><tt>reload</tt></tag>
5366 <item><p>cause the configuration of the service to be
5367 reloaded without actually stopping and restarting
5370 <tag><tt>force-reload</tt></tag>
5371 <item>cause the configuration to be reloaded if the
5372 service supports this, otherwise restart the
5376 The <tt>start</tt>, <tt>stop</tt>, <tt>restart</tt>, and
5377 <tt>force-reload</tt> options should be supported by all
5378 scripts in <file>/etc/init.d</file>, the <tt>reload</tt>
5383 The <file>init.d</file> scripts should ensure that they will
5384 behave sensibly if invoked with <tt>start</tt> when the
5385 service is already running, or with <tt>stop</tt> when it
5386 isn't, and that they don't kill unfortunately-named user
5387 processes. The best way to achieve this is usually to use
5388 <prgn>start-stop-daemon</prgn>.
5392 If a service reloads its configuration automatically (as
5393 in the case of <prgn>cron</prgn>, for example), the
5394 <tt>reload</tt> option of the <file>init.d</file> script
5395 should behave as if the configuration has been reloaded
5400 The <file>/etc/init.d</file> scripts must be treated as
5401 configuration files, either (if they are present in the
5402 package, that is, in the .deb file) by marking them as
5403 <tt>conffile</tt>s, or, (if they do not exist in the .deb)
5404 by managing them correctly in the maintainer scripts (see
5405 <ref id="config-files">). This is important since we want
5406 to give the local system administrator the chance to adapt
5407 the scripts to the local system, e.g., to disable a
5408 service without de-installing the package, or to specify
5409 some special command line options when starting a service,
5410 while making sure her changes aren't lost during the next
5415 These scripts should not fail obscurely when the
5416 configuration files remain but the package has been
5417 removed, as configuration files remain on the system after
5418 the package has been removed. Only when <prgn>dpkg</prgn>
5419 is executed with the <tt>--purge</tt> option will
5420 configuration files be removed. In particular, as the
5421 <file>/etc/init.d/<var>package</var></file> script itself is
5422 usually a <tt>conffile</tt>, it will remain on the system
5423 if the package is removed but not purged. Therefore, you
5424 should include a <tt>test</tt> statement at the top of the
5426 <example compact="compact">
5427 test -f <var>program-executed-later-in-script</var> || exit 0
5432 Often there are some variables in the <file>init.d</file>
5433 scripts whose values control the behaviour of the scripts,
5434 and which a system administrator is likely to want to
5435 change. As the scripts themselves are frequently
5436 <tt>conffile</tt>s, modifying them requires that the
5437 administrator merge in their changes each time the package
5438 is upgraded and the <tt>conffile</tt> changes. To ease
5439 the burden on the system administrator, such configurable
5440 values should not be placed directly in the script.
5441 Instead, they should be placed in a file in
5442 <file>/etc/default</file>, which typically will have the same
5443 base name as the <file>init.d</file> script. This extra file
5444 should be sourced by the script when the script runs. It
5445 must contain only variable settings and comments in POSIX
5446 <prgn>sh</prgn> format. It may either be a
5447 <tt>conffile</tt> or a configuration file maintained by
5448 the package maintainer scripts. See <ref id="config-files">
5453 To ensure that vital configurable values are always
5454 available, the <file>init.d</file> script should set default
5455 values for each of the shell variables it uses, either
5456 before sourcing the <file>/etc/default/</file> file or
5457 afterwards using something like the <tt>:
5458 ${VAR:=default}</tt> syntax. Also, the <file>init.d</file>
5459 script must behave sensibly and not fail if the
5460 <file>/etc/default</file> file is deleted.
5465 <heading>Interfacing with the initscript system</heading>
5468 Maintainers should use the abstraction layer provided by
5469 the <prgn>update-rc.d</prgn> and <prgn>invoke-rc.d</prgn>
5470 programs to deal with initscripts in their packages'
5471 scripts such as <prgn>postinst</prgn>, <prgn>prerm</prgn>
5472 and <prgn>postrm</prgn>.
5476 Directly managing the /etc/rc?.d links and directly
5477 invoking the <file>/etc/init.d/</file> initscripts should
5478 be done only by packages providing the initscript
5479 subsystem (such as <prgn>sysv-rct</prgn> and
5480 <prgn>file-rc</prgn>).
5484 <heading>Managing the links</heading>
5487 The program <prgn>update-rc.d</prgn> is provided for
5488 package maintainers to arrange for the proper creation and
5489 removal of <file>/etc/rc<var>n</var>.d</file> symbolic links,
5490 or their functional equivalent if another method is being
5491 used. This may be used by maintainers in their packages'
5492 <prgn>postinst</prgn> and <prgn>postrm</prgn> scripts.
5496 You must not include any <file>/etc/rc<var>n</var>.d</file>
5497 symbolic links in the actual archive or manually create or
5498 remove the symbolic links in maintainer scripts; you must
5499 use the <prgn>update-rc.d</prgn> program instead. (The
5500 former will fail if an alternative method of maintaining
5501 runlevel information is being used.) You must not include
5502 the <file>/etc/rc<var>n</var>.d</file> directories themselves
5503 in the archive either. (Only the <tt>sysvinit</tt>
5508 By default <prgn>update-rc.d</prgn> will start services in
5509 each of the multi-user state runlevels (2, 3, 4, and 5)
5510 and stop them in the halt runlevel (0), the single-user
5511 runlevel (1) and the reboot runlevel (6). The system
5512 administrator will have the opportunity to customize
5513 runlevels by simply adding, moving, or removing the
5514 symbolic links in <file>/etc/rc<var>n</var>.d</file> if
5515 symbolic links are being used, or by modifying
5516 <file>/etc/runlevel.conf</file> if the <tt>file-rc</tt> method
5521 To get the default behavior for your package, put in your
5522 <prgn>postinst</prgn> script
5523 <example compact="compact">
5524 update-rc.d <var>package</var> defaults
5526 and in your <prgn>postrm</prgn>
5527 <example compact="compact">
5528 if [ "$1" = purge ]; then
5529 update-rc.d <var>package</var> remove
5531 </example>. Note that if your package changes runlevels
5532 or priority, you may have to remove and recreate the links,
5533 since otherwise the old links may persist. Refer to the
5534 documentation of <prgn>update-rc.d</prgn>.
5538 This will use a default sequence number of 20. If it does
5539 not matter when or in which order the <file>init.d</file>
5540 script is run, use this default. If it does, then you
5541 should talk to the maintainer of the <prgn>sysvinit</prgn>
5542 package or post to <tt>debian-devel</tt>, and they will
5543 help you choose a number.
5547 For more information about using <tt>update-rc.d</tt>,
5548 please consult its manpage <manref name="update-rc.d"
5554 <heading>Running initscripts</heading>
5556 The program <prgn>invoke-rc.d</prgn> is provided to make
5557 it easier for package maintainers to properly invoke an
5558 initscript, obeying runlevel and other locally-defined
5559 constraints that might limit a package's right to start,
5560 stop and otherwise manage services. This program may be
5561 used by maintainers in their packages' scripts.
5565 The use of <prgn>invoke-rc.d</prgn> to invoke the
5566 <file>/etc/init.d/*</file> initscripts is strongly
5567 recommended<footnote>
5568 In the future, the use of invoke-rc.d to invoke
5569 initscripts shall be made mandatory. Maintainers are
5570 advised to switch to invoke-rc.d as soon as
5572 </footnote>, instead of calling them directly.
5576 By default, <prgn>invoke-rc.d</prgn> will pass any
5577 action requests (start, stop, reload, restart...) to the
5578 <file>/etc/init.d</file> script, filtering out requests
5579 to start or restart a service out of its intended
5584 Most packages will simply need to change:
5585 <example compact="compact">/etc/init.d/<package>
5586 <action></example> in their <prgn>postinst</prgn>
5587 and <prgn>prerm</prgn> scripts to:
5588 <example compact="compact">
5589 if [ -x /usr/sbin/invoke-rc.d ] ; then
5590 invoke-rc.d <var>package</var> <action>
5592 /etc/init.d/<var>package</var> <action>
5598 A package should register its initscript services using
5599 <prgn>update-rc.d</prgn> before it tries to invoke them
5600 using <prgn>invoke-rc.d</prgn>. Invocation of
5601 unregistered services may fail.
5605 For more information about using
5606 <prgn>invoke-rc.d</prgn>, please consult its manpage
5607 <manref name="invoke-rc.d" section="8">.
5613 <heading>Boot-time initialization</heading>
5616 There used to be another directory, <file>/etc/rc.boot</file>,
5617 which contained scripts which were run once per machine
5618 boot. This has been deprecated in favour of links from
5619 <file>/etc/rcS.d</file> to files in <file>/etc/init.d</file> as
5620 described in <ref id="/etc/init.d">. Packages must not
5621 place files in <file>/etc/rc.boot</file>.
5626 <heading>Example</heading>
5629 The <prgn>bind</prgn> DNS (nameserver) package wants to
5630 make sure that the nameserver is running in multiuser
5631 runlevels, and is properly shut down with the system. It
5632 puts a script in <file>/etc/init.d</file>, naming the script
5633 appropriately <tt>bind</tt>. As you can see, the script
5634 interprets the argument <tt>reload</tt> to send the
5635 nameserver a <tt>HUP</tt> signal (causing it to reload its
5636 configuration); this way the system administrator can say
5637 <tt>/etc/init.d/bind reload</tt> to reload the name
5638 server. The script has one configurable value, which can
5639 be used to pass parameters to the named program at
5640 startup; this value is read from
5641 <file>/etc/default/bind</file> (see below).
5645 <example compact="compact">
5648 # Original version by Robert Leslie
5649 # <rob@mars.org>, edited by iwj and cs
5651 test -x /usr/sbin/named || exit 0
5653 # Source defaults file.
5655 if [ -f /etc/default/bind ]; then
5662 echo -n "Starting domain name service: named"
5663 start-stop-daemon --start --quiet --exec /usr/sbin/named \
5668 echo -n "Stopping domain name service: named"
5669 start-stop-daemon --stop --quiet \
5670 --pidfile /var/run/named.pid --exec /usr/sbin/named
5674 echo -n "Restarting domain name service: named"
5675 start-stop-daemon --stop --quiet --oknodo \
5676 --pidfile /var/run/named.pid --exec /usr/sbin/named
5677 start-stop-daemon --start --verbose --exec /usr/sbin/named \
5681 force-reload|reload)
5682 echo -n "Reloading configuration of domain name service: named"
5683 start-stop-daemon --stop --signal 1 --quiet \
5684 --pidfile /var/run/named.pid --exec /usr/sbin/named
5688 echo "Usage: /etc/init.d/bind " \
5689 " {start|stop|restart|reload|force-reload}" >&2
5699 Complementing the above init script is a configuration
5700 file <file>/etc/default/bind</file>, which contains
5701 configurable parameters used by the script. This would be
5702 created by the <prgn>postinst</prgn> script if it was not
5703 already present, and removed on purge by the
5704 <prgn>postrm</prgn> script.
5705 <example compact="compact">
5706 # Specified parameters to pass to named. See named(8).
5707 # You may uncomment the following line, and edit to taste.
5713 Another example on which you can base your
5714 <file>/etc/init.d</file> scripts is found in
5715 <file>/etc/init.d/skeleton</file>.
5719 If this package is happy with the default setup from
5720 <prgn>update-rc.d</prgn>, namely an ordering number of 20
5721 and having named running in all runlevels, it can say in
5722 its <prgn>postinst</prgn>:
5723 <example compact="compact">
5724 update-rc.d bind defaults >/dev/null
5726 And in its <prgn>postrm</prgn>, to remove the links when the
5728 <example compact="compact">
5729 if [ "$1" = purge ]; then
5730 update-rc.d bind remove >/dev/null
5738 <heading>Console messages from <file>init.d</file> scripts</heading>
5741 This section describes the formats to be used for messages
5742 written to standard output by the <file>/etc/init.d</file>
5743 scripts. The intent is to improve the consistency of
5744 Debian's startup and shutdown look and feel. For this
5745 reason, please look very carefully at the details. We want
5746 the messages to have the same format in terms of wording,
5747 spaces, punctuation and case of letters.
5751 Here is a list of overall rules that you should use when you
5752 create output messages. They can be useful if you have a
5753 non-standard message that is not covered specifically in the
5760 Every message should fit in one line (fewer than 80
5761 characters), start with a capital letter and end with
5762 a period (<tt>.</tt>) and line feed (<tt>"\n"</tt>).
5766 If you want to express that the computer is working on
5767 something (that is, performing a specific task, not
5768 starting or stopping a program), we use an "ellipsis"
5769 (three dots: <tt>...</tt>). Note that we don't insert
5770 spaces before or after the dots. If the task has been
5771 completed we write <tt>done.</tt> and a line feed.
5775 Design your messages as if the computer is telling you
5776 what he is doing (let him be polite :-), but don't
5777 mention "him" directly. For example, if you think of
5779 <example compact="compact">
5780 I'm starting network daemons: nfsd mountd.
5783 <example compact="compact">
5784 Starting network daemons: nfsd mountd.
5791 There are standard message formats for the following
5792 situations. They should be used by the <tt>init.d</tt>
5799 <p>When daemons are started</p>
5802 If your script starts one or more daemons, the output
5803 should look like this (a single line, no leading
5805 <example compact="compact">
5806 Starting <var>description</var>: <var>daemon-1</var> ... <var>daemon-n</var>.
5808 The <var>description</var> should describe the
5809 subsystem the daemon or set of daemons are part of,
5810 while <var>daemon-1</var> up to <var>daemon-n</var>
5811 denote each daemon's name (typically the file name of
5816 For example, the output of <file>/etc/init.d/lpd</file>
5818 <example compact="compact">
5819 Starting printer spooler: lpd.
5824 This can be achieved by saying
5825 <example compact="compact">
5826 echo -n "Starting printer spooler: lpd"
5827 start-stop-daemon --start --quiet --exec /usr/sbin/lpd
5830 in the script. If you have more than one daemon to
5831 start, you should do the following:
5832 <example compact="compact">
5833 echo -n "Starting remote file system services:"
5834 echo -n " nfsd"; start-stop-daemon --start --quiet nfsd
5835 echo -n " mountd"; start-stop-daemon --start --quiet mountd
5836 echo -n " ugidd"; start-stop-daemon --start --quiet ugidd
5839 This makes it possible for the user to see what takes
5840 so long and when the final daemon has been started.
5841 You should be careful where to put spaces: in the
5842 example above the system administrator can easily
5843 comment out a line if he don't wants to start a
5844 specific daemon, while the displayed message still
5850 <p>When a system parameter is being set</p>
5853 If you have to set up different system parameters
5854 during the system boot, you should use this format:
5855 <example compact="compact">
5856 Setting <var>parameter</var> to "<var>value</var>".
5861 You can use a statement such as the following to get
5863 <example compact="compact">
5864 echo "Setting DNS domainname to \"$domainname\"."
5869 Note that the same symbol (<tt>"</tt>) is used for the left
5870 and right quotation marks. A grave accent (<tt>`</tt>) is
5871 not a quote character; neither is an apostrophe
5877 <p>When a daemon is stopped or restarted</p>
5880 When you stop or restart a daemon, you should issue a
5881 message identical to the startup message, except that
5882 <tt>Starting</tt> is replaced with <tt>Stopping</tt>
5883 or <tt>Restarting</tt> respectively.
5887 For example, stopping the printer daemon will like
5889 <example compact="compact">
5890 Stopping printer spooler: lpd.
5896 <p>When something is executed</p>
5899 There are several examples where you have to run a
5900 program at system startup or shutdown to perform a
5901 specific task, for example, setting the system's clock
5902 using <prgn>netdate</prgn> or killing all processes
5903 when the system shuts down. Your message should look
5905 <example compact="compact">
5906 Doing something very useful...done.
5908 You should print the <tt>done.</tt> immediately after
5909 the job has been completed, so that the user is
5910 informed why she has to wait. You can get this
5912 <example compact="compact">
5913 echo -n "Doing something very useful..."
5922 <p>When the configuration is reloaded</p>
5925 When a daemon is forced to reload its configuration
5926 files you should use the following format:
5927 <example compact="compact">
5928 Reloading <var>description</var> configuration...done.
5930 where <var>description</var> is the same as in the
5931 daemon starting message.
5939 <heading>Cron jobs</heading>
5942 Packages must not modify the configuration file
5943 <file>/etc/crontab</file>, and they must not modify the files in
5944 <file>/var/spool/cron/crontabs</file>.</p>
5947 If a package wants to install a job that has to be executed
5948 via cron, it should place a file with the name of the
5949 package in one or more of the following directories:
5950 <example compact="compact">
5955 As these directory names imply, the files within them are
5956 executed on a daily, weekly, or monthly basis,
5957 respectively. The exact times are listed in
5958 <file>/etc/crontab</file>.</p>
5961 All files installed in any of these directories must be
5962 scripts (e.g., shell scripts or Perl scripts) so that they
5963 can easily be modified by the local system administrator.
5964 In addition, they should be treated as configuration
5969 If a certain job has to be executed more frequently than
5970 daily, the package should install a file
5971 <file>/etc/cron.d/<var>package</var></file>. This file uses the
5972 same syntax as <file>/etc/crontab</file> and is processed by
5973 <prgn>cron</prgn> automatically. The file must also be
5974 treated as a configuration file. (Note that entries in the
5975 <file>/etc/cron.d</file> directory are not handled by
5976 <prgn>anacron</prgn>. Thus, you should only use this
5977 directory for jobs which may be skipped if the system is not
5981 The scripts or crontab entries in these directories should
5982 check if all necessary programs are installed before they
5983 try to execute them. Otherwise, problems will arise when a
5984 package was removed but not purged since configuration files
5985 are kept on the system in this situation.</p>
5989 <heading>Menus</heading>
5992 The Debian <tt>menu</tt> package provides a standard
5993 interface between packages providing applications and
5994 documents, and <em>menu programs</em> (either X window
5995 managers or text-based menu programs such as
5996 <prgn>pdmenu</prgn>).
6000 All packages that provide applications that need not be
6001 passed any special command line arguments for normal
6002 operation should register a menu entry for those
6003 applications, so that users of the <tt>menu</tt> package
6004 will automatically get menu entries in their window
6005 managers, as well in shells like <tt>pdmenu</tt>.
6009 Menu entries should follow the current menu policy.
6013 The menu policy can be found in the <tt>menu-policy</tt>
6014 files in the <tt>debian-policy</tt> package.
6015 It is also available from the Debian web mirrors at
6016 <tt><url name="/doc/packaging-manuals/menu-policy/"
6017 id="http://www.debian.org/doc/packaging-manuals/menu-policy/"></tt>
6018 and from the Debian archive mirrors at
6019 <tt><url name="/doc/package-developer/menu-policy.txt.gz"
6020 id="http://ftp.debian.org/debian/doc/package-developer/menu-policy.txt.gz"></tt>.
6024 Please also refer to the <em>Debian Menu System</em>
6025 documentation that comes with the <tt>menu</tt> package for
6026 information about how to register your applications and web
6032 <heading>Multimedia handlers</heading>
6035 MIME (Multipurpose Internet Mail Extensions, RFCs 2045-2049)
6036 is a mechanism for encoding files and data streams and
6037 providing meta-information about them, in particular their
6038 type (e.g. audio or video) and format (e.g. PNG, HTML,
6043 Registration of MIME type handlers allows programs like mail
6044 user agents and web browsers to invoke these handlers to
6045 view, edit or display MIME types they don't support directly.
6049 Packages which provide the ability to view/show/play,
6050 compose, edit or print MIME types should register themselves
6051 as such following the current MIME support policy.
6055 The MIME support policy can be found in the <tt>mime-policy</tt>
6056 files in the <tt>debian-policy</tt> package.
6057 It is also available from the Debian web mirrors at
6058 <tt><url name="/doc/packaging-manuals/mime-policy/"
6059 id="http://www.debian.org/doc/packaging-manuals/mime-policy/"></tt>
6060 and from the Debian archive mirrors at
6061 <tt><url name="/doc/package-developer/mime-policy.txt.gz"
6062 id="http://ftp.debian.org/debian/doc/package-developer/mime-policy.txt.gz"></tt>.
6068 <heading>Keyboard configuration</heading>
6071 To achieve a consistent keyboard configuration so that all
6072 applications interpret a keyboard event the same way, all
6073 programs in the Debian distribution must be configured to
6074 comply with the following guidelines.
6078 The following keys must have the specified interpretations:
6081 <tag><tt><--</tt></tag>
6082 <item>delete the character to the left of the cursor</item>
6084 <tag><tt>Delete</tt></tag>
6085 <item>delete the character to the right of the cursor</item>
6087 <tag><tt>Control+H</tt></tag>
6088 <item>emacs: the help prefix</item>
6091 The interpretation of any keyboard events should be
6092 independent of the terminal that is used, be it a virtual
6093 console, an X terminal emulator, an rlogin/telnet session,
6098 The following list explains how the different programs
6099 should be set up to achieve this:
6105 <tt><--</tt> generates <tt>KB_BackSpace</tt> in X.
6109 <tt>Delete</tt> generates <tt>KB_Delete</tt> in X.
6113 X translations are set up to make
6114 <tt>KB_Backspace</tt> generate ASCII DEL, and to make
6115 <tt>KB_Delete</tt> generate <tt>ESC [ 3 ~</tt> (this
6116 is the vt220 escape code for the "delete character"
6117 key). This must be done by loading the X resources
6118 using <prgn>xrdb</prgn> on all local X displays, not
6119 using the application defaults, so that the
6120 translation resources used correspond to the
6121 <prgn>xmodmap</prgn> settings.
6125 The Linux console is configured to make
6126 <tt><--</tt> generate DEL, and <tt>Delete</tt>
6127 generate <tt>ESC [ 3 ~</tt>.
6131 X applications are configured so that <tt><</tt>
6132 deletes left, and <tt>Delete</tt> deletes right. Motif
6133 applications already work like this.
6137 Terminals should have <tt>stty erase ^?</tt> .
6141 The <tt>xterm</tt> terminfo entry should have <tt>ESC
6142 [ 3 ~</tt> for <tt>kdch1</tt>, just as for
6143 <tt>TERM=linux</tt> and <tt>TERM=vt220</tt>.
6147 Emacs is programmed to map <tt>KB_Backspace</tt> or
6148 the <tt>stty erase</tt> character to
6149 <tt>delete-backward-char</tt>, and <tt>KB_Delete</tt>
6150 or <tt>kdch1</tt> to <tt>delete-forward-char</tt>, and
6151 <tt>^H</tt> to <tt>help</tt> as always.
6155 Other applications use the <tt>stty erase</tt>
6156 character and <tt>kdch1</tt> for the two delete keys,
6157 with ASCII DEL being "delete previous character" and
6158 <tt>kdch1</tt> being "delete character under
6166 This will solve the problem except for the following
6173 Some terminals have a <tt><--</tt> key that cannot
6174 be made to produce anything except <tt>^H</tt>. On
6175 these terminals Emacs help will be unavailable on
6176 <tt>^H</tt> (assuming that the <tt>stty erase</tt>
6177 character takes precedence in Emacs, and has been set
6178 correctly). <tt>M-x help</tt> or <tt>F1</tt> (if
6179 available) can be used instead.
6183 Some operating systems use <tt>^H</tt> for <tt>stty
6184 erase</tt>. However, modern telnet versions and all
6185 rlogin versions propagate <tt>stty</tt> settings, and
6186 almost all UNIX versions honour <tt>stty erase</tt>.
6187 Where the <tt>stty</tt> settings are not propagated
6188 correctly, things can be made to work by using
6189 <tt>stty</tt> manually.
6193 Some systems (including previous Debian versions) use
6194 <prgn>xmodmap</prgn> to arrange for both
6195 <tt><--</tt> and <tt>Delete</tt> to generate
6196 <tt>KB_Delete</tt>. We can change the behavior of
6197 their X clients using the same X resources that we use
6198 to do it for our own clients, or configure our clients
6199 using their resources when things are the other way
6200 around. On displays configured like this
6201 <tt>Delete</tt> will not work, but <tt><--</tt>
6206 Some operating systems have different <tt>kdch1</tt>
6207 settings in their <tt>terminfo</tt> database for
6208 <tt>xterm</tt> and others. On these systems the
6209 <tt>Delete</tt> key will not work correctly when you
6210 log in from a system conforming to our policy, but
6211 <tt><--</tt> will.
6218 <heading>Environment variables</heading>
6221 A program must not depend on environment variables to get
6222 reasonable defaults. (That's because these environment
6223 variables would have to be set in a system-wide
6224 configuration file like <file>/etc/profile</file>, which is not
6225 supported by all shells.)
6229 If a program usually depends on environment variables for its
6230 configuration, the program should be changed to fall back to
6231 a reasonable default configuration if these environment
6232 variables are not present. If this cannot be done easily
6233 (e.g., if the source code of a non-free program is not
6234 available), the program must be replaced by a small
6235 "wrapper" shell script which sets the environment variables
6236 if they are not already defined, and calls the original program.
6240 Here is an example of a wrapper script for this purpose:
6242 <example compact="compact">
6244 BAR=${BAR:-/var/lib/fubar}
6246 exec /usr/lib/foo/foo "$@"
6251 Furthermore, as <file>/etc/profile</file> is a configuration
6252 file of the <prgn>base-files</prgn> package, other packages must
6253 not put any environment variables or other commands into that
6262 <heading>Files</heading>
6265 <heading>Binaries</heading>
6268 Two different packages must not install programs with
6269 different functionality but with the same filenames. (The
6270 case of two programs having the same functionality but
6271 different implementations is handled via "alternatives" or
6272 the "Conflicts" mechanism. See <ref id="maintscripts"> and
6273 <ref id="conflicts"> respectively.) If this case happens,
6274 one of the programs must be renamed. The maintainers should
6275 report this to the <tt>debian-devel</tt> mailing list and
6276 try to find a consensus about which program will have to be
6277 renamed. If a consensus cannot be reached, <em>both</em>
6278 programs must be renamed.
6282 By default, when a package is being built, any binaries
6283 created should include debugging information, as well as
6284 being compiled with optimization. You should also turn on
6285 as many reasonable compilation warnings as possible; this
6286 makes life easier for porters, who can then look at build
6287 logs for possible problems. For the C programming language,
6288 this means the following compilation parameters should be
6290 <example compact="compact">
6292 CFLAGS = -O2 -g -Wall # sane warning options vary between programs
6294 install -s # (or use strip on the files in debian/tmp)
6299 Note that by default all installed binaries should be stripped,
6300 either by using the <tt>-s</tt> flag to
6301 <prgn>install</prgn>, or by calling <prgn>strip</prgn> on
6302 the binaries after they have been copied into
6303 <file>debian/tmp</file> but before the tree is made into a
6308 Although binaries in the build tree should be compiled with
6309 debugging information by default, it can often be difficult
6310 to debug programs if they are also subjected to compiler
6311 optimization. For this reason, it is recommended to support
6312 the standardized environment
6313 variable <tt>DEB_BUILD_OPTIONS</tt>. This variable can
6314 contain several flags to change how a package is compiled
6322 The presence of this string means that the package
6323 should be compiled with a minimum of optimization.
6324 For C programs, it is best to add <tt>-O0</tt>
6325 to <tt>CFLAGS</tt> (although this is usually the
6326 default). Some programs might fail to build or run at
6327 this level of optimization; it may be necessary to
6328 use <tt>-O1</tt>, for example.
6332 This string means that the debugging symbols should
6333 not be stripped from the binary during installation,
6334 so that debugging information may be included in the package.
6340 The following makefile snippet is an example of how one may
6341 implement the build options; you will probably have to
6342 massage this example in order to make it work for your
6344 <example compact="compact">
6347 INSTALL_FILE = $(INSTALL) -p -o root -g root -m 644
6348 INSTALL_PROGRAM = $(INSTALL) -p -o root -g root -m 755
6349 INSTALL_SCRIPT = $(INSTALL) -p -o root -g root -m 755
6350 INSTALL_DIR = $(INSTALL) -p -d -o root -g root -m 755
6352 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
6357 ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
6358 INSTALL_PROGRAM += -s
6364 It is up to the package maintainer to decide what
6365 compilation options are best for the package. Certain
6366 binaries (such as computationally-intensive programs) will
6367 function better with certain flags (<tt>-O3</tt>, for
6368 example); feel free to use them. Please use good judgment
6369 here. Don't use flags for the sake of it; only use them
6370 if there is good reason to do so. Feel free to override
6371 the upstream author's ideas about which compilation
6372 options are best: they are often inappropriate for our
6378 <sect id="libraries">
6379 <heading>Libraries</heading>
6382 The shared version of a library must be compiled with
6383 <tt>-fPIC</tt>, and the static version must not be. In other
6384 words, each source unit (<tt>*.c</tt>, for example, for C files)
6385 will need to be compiled twice.
6389 You must specify the gcc option <tt>-D_REENTRANT</tt>
6390 when building a library (either static or shared) to make
6391 the library compatible with LinuxThreads.
6395 Although not enforced by the build tools, shared libraries
6396 must be linked against all libraries that they use symbols from
6397 in the same way that binaries are. This ensures the correct
6398 functioning of the <qref id="sharedlibs-shlibdeps">shlibs</qref>
6399 system and guarantees that all libraries can be safely opened
6400 with <tt>dlopen()</tt>. Packagers may wish to use the gcc
6401 option <tt>-Wl,-z,defs</tt> when building a shared library.
6402 Since this option enforces symbol resolution at build time,
6403 a missing library reference will be caught early as a fatal
6408 All installed shared libraries should be stripped with
6409 <example compact="compact">
6410 strip --strip-unneeded <var>your-lib</var>
6412 (The option <tt>--strip-unneeded</tt> makes
6413 <prgn>strip</prgn> remove only the symbols which aren't
6414 needed for relocation processing.) Shared libraries can
6415 function perfectly well when stripped, since the symbols for
6416 dynamic linking are in a separate part of the ELF object
6418 You might also want to use the options
6419 <tt>--remove-section=.comment</tt> and
6420 <tt>--remove-section=.note</tt> on both shared libraries
6421 and executables, and <tt>--strip-debug</tt> on static
6427 Note that under some circumstances it may be useful to
6428 install a shared library unstripped, for example when
6429 building a separate package to support debugging.
6433 Shared object files (often <file>.so</file> files) that are not
6434 public libraries, that is, they are not meant to be linked
6435 to by third party executables (binaries of other packages),
6436 should be installed in subdirectories of the
6437 <file>/usr/lib</file> directory. Such files are exempt from the
6438 rules that govern ordinary shared libraries, except that
6439 they must not be installed executable and should be
6441 A common example are the so-called "plug-ins",
6442 internal shared objects that are dynamically loaded by
6443 programs using <manref name="dlopen" section="3">.
6448 Packages containing shared libraries that may be linked to
6449 by other packages' binaries, but which for some
6450 <em>compelling</em> reason can not be installed in
6451 <file>/usr/lib</file> directory, may install the shared library
6452 files in subdirectories of the <file>/usr/lib</file> directory,
6453 in which case they should arrange to add that directory in
6454 <file>/etc/ld.so.conf</file> in the package's post-installation
6455 script, and remove it in the package's post-removal script.
6459 An ever increasing number of packages are using
6460 <prgn>libtool</prgn> to do their linking. The latest GNU
6461 libtools (>= 1.3a) can take advantage of the metadata in the
6462 installed <prgn>libtool</prgn> archive files (<file>*.la</file>
6463 files). The main advantage of <prgn>libtool</prgn>'s
6464 <file>.la</file> files is that it allows <prgn>libtool</prgn> to
6465 store and subsequently access metadata with respect to the
6466 libraries it builds. <prgn>libtool</prgn> will search for
6467 those files, which contain a lot of useful information about
6468 a library (such as library dependency information for static
6469 linking). Also, they're <em>essential</em> for programs
6470 using <tt>libltdl</tt>.<footnote>
6471 Although <prgn>libtool</prgn> is fully capable of
6472 linking against shared libraries which don't have
6473 <tt>.la</tt> files, as it is a mere shell script it can
6474 add considerably to the build time of a
6475 <prgn>libtool</prgn>-using package if that shell script
6476 has to derive all this information from first principles
6477 for each library every time it is linked. With the
6478 advent of <prgn>libtool</prgn> version 1.4 (and to a
6479 lesser extent <prgn>libtool</prgn> version 1.3), the
6480 <file>.la</file> files also store information about
6481 inter-library dependencies which cannot necessarily be
6482 derived after the <file>.la</file> file is deleted.
6487 Packages that use <prgn>libtool</prgn> to create shared
6488 libraries should include the <file>.la</file> files in the
6489 <tt>-dev</tt> package, unless the package relies on
6490 <tt>libtool</tt>'s <tt>libltdl</tt> library, in which case
6491 the <tt>.la</tt> files must go in the run-time library
6496 You must make sure that you use only released versions of
6497 shared libraries to build your packages; otherwise other
6498 users will not be able to run your binaries
6499 properly. Producing source packages that depend on
6500 unreleased compilers is also usually a bad
6507 <heading>Shared libraries</heading>
6509 This section has moved to <ref id="sharedlibs">.
6515 <heading>Scripts</heading>
6518 All command scripts, including the package maintainer
6519 scripts inside the package and used by <prgn>dpkg</prgn>,
6520 should have a <tt>#!</tt> line naming the shell to be used
6525 In the case of Perl scripts this should be
6526 <tt>#!/usr/bin/perl</tt>.
6530 Shell scripts (<prgn>sh</prgn> and <prgn>bash</prgn>)
6531 should almost certainly start with <tt>set -e</tt> so that
6532 errors are detected. Every script should use
6533 <tt>set -e</tt> or check the exit status of <em>every</em>
6538 The standard shell interpreter <file>/bin/sh</file> can be a
6539 symbolic link to any POSIX compatible shell, if <tt>echo
6540 -n</tt> does not generate a newline.<footnote>
6541 Debian policy specifies POSIX behavior for
6542 <file>/bin/sh</file>, but <tt>echo -n</tt> has widespread
6543 use in the Linux community (in particular including this
6544 policy, the Linux kernel source, many Debian scripts,
6545 etc.). This <tt>echo -n</tt> mechanism is valid but not
6546 required under POSIX, hence this explicit addition.
6547 Also, rumour has it that this shall be mandated under
6550 Thus, shell scripts specifying <file>/bin/sh</file> as
6551 interpreter should only use POSIX features. If a script
6552 requires non-POSIX features from the shell interpreter, the
6553 appropriate shell must be specified in the first line of the
6554 script (e.g., <tt>#!/bin/bash</tt>) and the package must
6555 depend on the package providing the shell (unless the shell
6556 package is marked "Essential", as in the case of
6561 You may wish to restrict your script to POSIX features when
6562 possible so that it may use <file>/bin/sh</file> as its
6563 interpreter. If your script works with <prgn>dash</prgn>
6564 (originally called <prgn>ash</prgn>), it's probably POSIX
6565 compliant, but if you are in doubt, use
6566 <file>/bin/bash</file>.
6570 Perl scripts should check for errors when making any
6571 system calls, including <tt>open</tt>, <tt>print</tt>,
6572 <tt>close</tt>, <tt>rename</tt> and <tt>system</tt>.
6576 <prgn>csh</prgn> and <prgn>tcsh</prgn> should be avoided as
6577 scripting languages. See <em>Csh Programming Considered
6578 Harmful</em>, one of the <tt>comp.unix.*</tt> FAQs, which
6579 can be found at <url id="http://language.perl.com/versus/csh.whynot">.
6580 If an upstream package comes with <prgn>csh</prgn> scripts
6581 then you must make sure that they start with
6582 <tt>#!/bin/csh</tt> and make your package depend on the
6583 <prgn>c-shell</prgn> virtual package.
6587 Any scripts which create files in world-writeable
6588 directories (e.g., in <file>/tmp</file>) must use a
6589 mechanism which will fail if a file with the same name
6594 The Debian base system provides the <prgn>tempfile</prgn>
6595 and <prgn>mktemp</prgn> utilities for use by scripts for
6602 <heading>Symbolic links</heading>
6605 In general, symbolic links within a top-level directory
6606 should be relative, and symbolic links pointing from one
6607 top-level directory into another should be absolute. (A
6608 top-level directory is a sub-directory of the root
6609 directory <file>/</file>.)
6613 In addition, symbolic links should be specified as short as
6614 possible, i.e., link targets like <file>foo/../bar</file> are
6619 Note that when creating a relative link using
6620 <prgn>ln</prgn> it is not necessary for the target of the
6621 link to exist relative to the working directory you're
6622 running <prgn>ln</prgn> from, nor is it necessary to change
6623 directory to the directory where the link is to be made.
6624 Simply include the string that should appear as the target
6625 of the link (this will be a pathname relative to the
6626 directory in which the link resides) as the first argument
6631 For example, in your <prgn>Makefile</prgn> or
6632 <file>debian/rules</file>, you can do things like:
6633 <example compact="compact">
6634 ln -fs gcc $(prefix)/bin/cc
6635 ln -fs gcc debian/tmp/usr/bin/cc
6636 ln -fs ../sbin/sendmail $(prefix)/bin/runq
6637 ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
6642 A symbolic link pointing to a compressed file should always
6643 have the same file extension as the referenced file. (For
6644 example, if a file <file>foo.gz</file> is referenced by a
6645 symbolic link, the filename of the link has to end with
6646 "<file>.gz</file>" too, as in <file>bar.gz</file>.)
6651 <heading>Device files</heading>
6654 Packages must not include device files in the package file
6659 If a package needs any special device files that are not
6660 included in the base system, it must call
6661 <prgn>MAKEDEV</prgn> in the <prgn>postinst</prgn> script,
6662 after notifying the user<footnote>
6663 This notification could be done via a (low-priority)
6664 debconf message, or an echo (printf) statement.
6669 Packages must not remove any device files in the
6670 <prgn>postrm</prgn> or any other script. This is left to the
6671 system administrator.
6675 Debian uses the serial devices
6676 <file>/dev/ttyS*</file>. Programs using the old
6677 <file>/dev/cu*</file> devices should be changed to use
6678 <file>/dev/ttyS*</file>.
6682 <sect id="config-files">
6683 <heading>Configuration files</heading>
6686 <heading>Definitions</heading>
6690 <tag>configuration file</tag>
6692 A file that affects the operation of a program, or
6693 provides site- or host-specific information, or
6694 otherwise customizes the behavior of a program.
6695 Typically, configuration files are intended to be
6696 modified by the system administrator (if needed or
6697 desired) to conform to local policy or to provide
6698 more useful site-specific behavior.
6701 <tag><tt>conffile</tt></tag>
6703 A file listed in a package's <tt>conffiles</tt>
6704 file, and is treated specially by <prgn>dpkg</prgn>
6705 (see <ref id="configdetails">).
6711 The distinction between these two is important; they are
6712 not interchangeable concepts. Almost all
6713 <tt>conffile</tt>s are configuration files, but many
6714 configuration files are not <tt>conffiles</tt>.
6718 Note that a script that embeds configuration information
6719 (such as most of the files in <file>/etc/default</file> and
6720 <file>/etc/cron.{daily,weekly,monthly}</file>) is de-facto a
6721 configuration file and should be treated as such.
6726 <heading>Location</heading>
6729 Any configuration files created or used by your package
6730 must reside in <file>/etc</file>. If there are several,
6731 consider creating a subdirectory of <file>/etc</file>
6732 named after your package.
6736 If your package creates or uses configuration files
6737 outside of <file>/etc</file>, and it is not feasible to modify
6738 the package to use <file>/etc</file> directly, put the files
6739 in <file>/etc</file> and create symbolic links to those files
6740 from the location that the package requires.
6745 <heading>Behavior</heading>
6748 Configuration file handling must conform to the following
6750 <list compact="compact">
6752 local changes must be preserved during a package
6756 configuration files must be preserved when the
6757 package is removed, and only deleted when the
6764 The easy way to achieve this behavior is to make the
6765 configuration file a <tt>conffile</tt>. This is
6766 appropriate only if it is possible to distribute a default
6767 version that will work for most installations, although
6768 some system administrators may choose to modify it. This
6769 implies that the default version will be part of the
6770 package distribution, and must not be modified by the
6771 maintainer scripts during installation (or at any other
6776 In order to ensure that local changes are preserved
6777 correctly, no package may contain or make hard links to
6778 conffiles.<footnote>
6779 Rationale: There are two problems with hard links.
6780 The first is that some editors break the link while
6781 editing one of the files, so that the two files may
6782 unwittingly become unlinked and different. The second
6783 is that <prgn>dpkg</prgn> might break the hard link
6784 while upgrading <tt>conffile</tt>s.
6789 The other way to do it is via the maintainer scripts. In
6790 this case, the configuration file must not be listed as a
6791 <tt>conffile</tt> and must not be part of the package
6792 distribution. If the existence of a file is required for
6793 the package to be sensibly configured it is the
6794 responsibility of the package maintainer to provide
6795 maintainer scripts which correctly create, update and
6796 maintain the file and remove it on purge. (See <ref
6797 id="maintainerscripts"> for more information.) These
6798 scripts must be idempotent (i.e., must work correctly if
6799 <prgn>dpkg</prgn> needs to re-run them due to errors
6800 during installation or removal), must cope with all the
6801 variety of ways <prgn>dpkg</prgn> can call maintainer
6802 scripts, must not overwrite or otherwise mangle the user's
6803 configuration without asking, must not ask unnecessary
6804 questions (particularly during upgrades), and otherwise be
6809 The scripts are not required to configure every possible
6810 option for the package, but only those necessary to get
6811 the package running on a given system. Ideally the
6812 sysadmin should not have to do any configuration other
6813 than that done (semi-)automatically by the
6814 <prgn>postinst</prgn> script.
6818 A common practice is to create a script called
6819 <file><var>package</var>-configure</file> and have the
6820 package's <prgn>postinst</prgn> call it if and only if the
6821 configuration file does not already exist. In certain
6822 cases it is useful for there to be an example or template
6823 file which the maintainer scripts use. Such files should
6824 be in <file>/usr/share/<var>package</var></file> or
6825 <file>/usr/lib/<var>package</var></file> (depending on whether
6826 they are architecture-independent or not). There should
6827 be symbolic links to them from
6828 <file>/usr/share/doc/<var>package</var>/examples</file> if
6829 they are examples, and should be perfectly ordinary
6830 <prgn>dpkg</prgn>-handled files (<em>not</em>
6831 configuration files).
6835 These two styles of configuration file handling must
6836 not be mixed, for that way lies madness:
6837 <prgn>dpkg</prgn> will ask about overwriting the file
6838 every time the package is upgraded.
6843 <heading>Sharing configuration files</heading>
6846 Packages which specify the same file as a
6847 <tt>conffile</tt> must be tagged as <em>conflicting</em>
6848 with each other. (This is an instance of the general rule
6849 about not sharing files. Note that neither alternatives
6850 nor diversions are likely to be appropriate in this case;
6851 in particular, <prgn>dpkg</prgn> does not handle diverted
6852 <tt>conffile</tt>s well.)
6856 The maintainer scripts must not alter a <tt>conffile</tt>
6857 of <em>any</em> package, including the one the scripts
6862 If two or more packages use the same configuration file
6863 and it is reasonable for both to be installed at the same
6864 time, one of these packages must be defined as
6865 <em>owner</em> of the configuration file, i.e., it will be
6866 the package which handles that file as a configuration
6867 file. Other packages that use the configuration file must
6868 depend on the owning package if they require the
6869 configuration file to operate. If the other package will
6870 use the configuration file if present, but is capable of
6871 operating without it, no dependency need be declared.
6875 If it is desirable for two or more related packages to
6876 share a configuration file <em>and</em> for all of the
6877 related packages to be able to modify that configuration
6878 file, then the following should be done:
6879 <enumlist compact="compact">
6881 One of the related packages (the "owning" package)
6882 will manage the configuration file with maintainer
6883 scripts as described in the previous section.
6886 The owning package should also provide a program
6887 that the other packages may use to modify the
6891 The related packages must use the provided program
6892 to make any desired modifications to the
6893 configuration file. They should either depend on
6894 the core package to guarantee that the configuration
6895 modifier program is available or accept gracefully
6896 that they cannot modify the configuration file if it
6897 is not. (This is in addition to the fact that the
6898 configuration file may not even be present in the
6905 Sometimes it's appropriate to create a new package which
6906 provides the basic infrastructure for the other packages
6907 and which manages the shared configuration files. (The
6908 <tt>sgml-base</tt> package is a good example.)
6913 <heading>User configuration files ("dotfiles")</heading>
6916 The files in <file>/etc/skel</file> will automatically be
6917 copied into new user accounts by <prgn>adduser</prgn>.
6918 No other program should reference the files in
6919 <file>/etc/skel</file>.
6923 Therefore, if a program needs a dotfile to exist in
6924 advance in <file>$HOME</file> to work sensibly, that dotfile
6925 should be installed in <file>/etc/skel</file> and treated as a
6930 However, programs that require dotfiles in order to
6931 operate sensibly are a bad thing, unless they do create
6932 the dotfiles themselves automatically.
6936 Furthermore, programs should be configured by the Debian
6937 default installation to behave as closely to the upstream
6938 default behaviour as possible.
6942 Therefore, if a program in a Debian package needs to be
6943 configured in some way in order to operate sensibly, that
6944 should be done using a site-wide configuration file placed
6945 in <file>/etc</file>. Only if the program doesn't support a
6946 site-wide default configuration and the package maintainer
6947 doesn't have time to add it may a default per-user file be
6948 placed in <file>/etc/skel</file>.
6952 <file>/etc/skel</file> should be as empty as we can make it.
6953 This is particularly true because there is no easy (or
6954 necessarily desirable) mechanism for ensuring that the
6955 appropriate dotfiles are copied into the accounts of
6956 existing users when a package is installed.
6962 <heading>Log files</heading>
6964 Log files should usually be named
6965 <file>/var/log/<var>package</var>.log</file>. If you have many
6966 log files, or need a separate directory for permission
6967 reasons (<file>/var/log</file> is writable only by
6968 <file>root</file>), you should usually create a directory named
6969 <file>/var/log/<var>package</var></file> and place your log
6974 Log files must be rotated occasionally so that they don't
6975 grow indefinitely; the best way to do this is to drop a log
6976 rotation configuration file into the directory
6977 <file>/etc/logrotate.d</file> and use the facilities provided by
6978 logrotate.<footnote>
6980 The traditional approach to log files has been to set up
6981 <em>ad hoc</em> log rotation schemes using simple shell
6982 scripts and cron. While this approach is highly
6983 customizable, it requires quite a lot of sysadmin work.
6984 Even though the original Debian system helped a little
6985 by automatically installing a system which can be used
6986 as a template, this was deemed not enough.
6990 The use of <prgn>logrotate</prgn>, a program developed
6991 by Red Hat, is better, as it centralizes log management.
6992 It has both a configuration file
6993 (<file>/etc/logrotate.conf</file>) and a directory where
6994 packages can drop their individual log rotation
6995 configurations (<file>/etc/logrotate.d</file>).
6998 Here is a good example for a logrotate config
6999 file (for more information see <manref name="logrotate"
7001 <example compact="compact">
7002 /var/log/foo/*.log {
7007 /etc/init.d/foo force-reload
7011 This rotates all files under <file>/var/log/foo</file>, saves 12
7012 compressed generations, and forces the daemon to reload its
7013 configuration information after the log rotation.
7017 Log files should be removed when the package is
7018 purged (but not when it is only removed). This should be
7019 done by the <prgn>postrm</prgn> script when it is called
7020 with the argument <tt>purge</tt> (see <ref
7021 id="removedetails">).
7026 <heading>Permissions and owners</heading>
7029 The rules in this section are guidelines for general use.
7030 If necessary you may deviate from the details below.
7031 However, if you do so you must make sure that what is done
7032 is secure and you should try to be as consistent as possible
7033 with the rest of the system. You should probably also
7034 discuss it on <prgn>debian-devel</prgn> first.
7038 Files should be owned by <tt>root.root</tt>, and made
7039 writable only by the owner and universally readable (and
7040 executable, if appropriate), that is mode 644 or 755.
7044 Directories should be mode 755 or (for group-writability)
7045 mode 2775. The ownership of the directory should be
7046 consistent with its mode: if a directory is mode 2775, it
7047 should be owned by the group that needs write access to
7052 Setuid and setgid executables should be mode 4755 or 2755
7053 respectively, and owned by the appropriate user or group.
7054 They should not be made unreadable (modes like 4711 or
7055 2711 or even 4111); doing so achieves no extra security,
7056 because anyone can find the binary in the freely available
7057 Debian package; it is merely inconvenient. For the same
7058 reason you should not restrict read or execute permissions
7059 on non-set-id executables.
7063 Some setuid programs need to be restricted to particular
7064 sets of users, using file permissions. In this case they
7065 should be owned by the uid to which they are set-id, and by
7066 the group which should be allowed to execute them. They
7067 should have mode 4754; again there is no point in making
7068 them unreadable to those users who must not be allowed to
7073 It is possible to arrange that the system administrator can
7074 reconfigure the package to correspond to their local
7075 security policy by changing the permissions on a binary:
7076 they can do this by using <prgn>dpkg-statoverride</prgn>, as
7077 described below.<footnote>
7078 Ordinary files installed by <prgn>dpkg</prgn> (as
7079 opposed to <tt>conffile</tt>s and other similar objects)
7080 normally have their permissions reset to the distributed
7081 permissions when the package is reinstalled. However,
7082 the use of <prgn>dpkg-statoverride</prgn> overrides this
7083 default behaviour. If you use this method, you should
7084 remember to describe <prgn>dpkg-statoverride</prgn> in
7085 the package documentation; being a relatively new
7086 addition to Debian, it is probably not yet well-known.
7088 Another method you should consider is to create a group for
7089 people allowed to use the program(s) and make any setuid
7090 executables executable only by that group.
7094 If you need to create a new user or group for your package
7095 there are two possibilities. Firstly, you may need to
7096 make some files in the binary package be owned by this
7097 user or group, or you may need to compile the user or
7098 group id (rather than just the name) into the binary
7099 (though this latter should be avoided if possible, as in
7100 this case you need a statically allocated id).</p>
7103 If you need a statically allocated id, you must ask for a
7104 user or group id from the <tt>base-passwd</tt> maintainer,
7105 and must not release the package until you have been
7106 allocated one. Once you have been allocated one you must
7107 either make the package depend on a version of the
7108 <tt>base-passwd</tt> package with the id present in
7109 <file>/etc/passwd</file> or <file>/etc/group</file>, or arrange for
7110 your package to create the user or group itself with the
7111 correct id (using <tt>adduser</tt>) in its
7112 <prgn>preinst</prgn> or <prgn>postinst</prgn>. (Doing it in
7113 the <prgn>postinst</prgn> is to be preferred if it is
7114 possible, otherwise a pre-dependency will be needed on the
7115 <tt>adduser</tt> package.)
7119 On the other hand, the program might be able to determine
7120 the uid or gid from the user or group name at runtime, so
7121 that a dynamically allocated id can be used. In this case
7122 you should choose an appropriate user or group name,
7123 discussing this on <prgn>debian-devel</prgn> and checking
7124 with the <package/base-passwd/ maintainer that it is unique and that
7125 they do not wish you to use a statically allocated id
7126 instead. When this has been checked you must arrange for
7127 your package to create the user or group if necessary using
7128 <prgn>adduser</prgn> in the <prgn>preinst</prgn> or
7129 <prgn>postinst</prgn> script (again, the latter is to be
7130 preferred if it is possible).
7134 Note that changing the numeric value of an id associated
7135 with a name is very difficult, and involves searching the
7136 file system for all appropriate files. You need to think
7137 carefully whether a static or dynamic id is required, since
7138 changing your mind later will cause problems.
7141 <sect1><heading>The use of <prgn>dpkg-statoverride</prgn></heading>
7143 This section is not intended as policy, but as a
7144 description of the use of <prgn>dpkg-statoverride</prgn>.
7148 <prgn>dpkg-statoverride</prgn> is a replacement for the
7149 deprecated <tt>suidmanager</tt> package. Packages which
7150 previously used <tt>suidmanager</tt> should have a
7151 <tt>Conflicts: suidmanager (<< 0.50)</tt> entry (or even
7152 <tt>(<< 0.52)</tt>), and calls to <tt>suidregister</tt>
7153 and <tt>suidunregister</tt> should now be simply removed
7154 from the maintainer scripts.
7158 If a system administrator wishes to have a file (or
7159 directory or other such thing) installed with owner and
7160 permissions different from those in the distributed Debian
7161 package, he can use the <prgn>dpkg-statoverride</prgn>
7162 program to instruct <prgn>dpkg</prgn> to use the different
7163 settings every time the file is installed. Thus the
7164 package maintainer should distribute the files with their
7165 normal permissions, and leave it for the system
7166 administrator to make any desired changes. For example, a
7167 daemon which is normally required to be setuid root, but
7168 in certain situations could be used without being setuid,
7169 should be installed setuid in the <tt>.deb</tt>. Then the
7170 local system administrator can change this if they wish.
7171 If there are two standard ways of doing it, the package
7172 maintainer can use <tt>debconf</tt> to find out the
7173 preference, and call <prgn>dpkg-statoverride</prgn> in the
7174 maintainer script if necessary to accommodate the system
7175 administrator's choice.
7179 Given the above, <prgn>dpkg-statoverride</prgn> is
7180 essentially a tool for system administrators and would not
7181 normally be needed in the maintainer scripts. There is
7182 one type of situation, though, where calls to
7183 <prgn>dpkg-statoverride</prgn> would be needed in the
7184 maintainer scripts, and that involves packages which use
7185 dynamically allocated user or group ids. In such a
7186 situation, something like the following idiom can be very
7187 helpful in the package's <prgn>postinst</prgn>, where
7188 <tt>sysuser</tt> is a dynamically allocated id:
7190 for i in /usr/bin/foo /usr/sbin/bar
7192 if ! dpkg-statoverride --list $i >/dev/null
7194 dpkg-statoverride --update --add sysuser root 4755 $i
7198 The corresponding <tt>dpkg-statoverride --remove</tt>
7199 calls can then be made unconditionally when the package is
7207 <chapt id="customized-programs">
7208 <heading>Customized programs</heading>
7210 <sect id="arch-spec">
7211 <heading>Architecture specification strings</heading>
7214 If a program needs to specify an <em>architecture specification
7215 string</em> in some place, the following format should be
7216 used: <var>arch</var>-<var>os</var><footnote>
7217 The following architectures and operating systems are
7218 currently recognised by <prgn>dpkg-architecture</prgn>.
7219 The architecture, <tt><var>arch</var></tt>, is one of
7220 the following: <tt>alpha</tt>, <tt>arm</tt>,
7221 <tt>hppa</tt>, <tt>i386</tt>, <tt>ia64</tt>,
7222 <tt>m68k</tt>, <tt>mips</tt>, <tt>mipsel</tt>,
7223 <tt>powerpc</tt>, <tt>s390</tt>, <tt>sh</tt>,
7224 <tt>sheb</tt>, <tt>sparc</tt> and <tt>sparc64</tt>. The
7225 operating system, <tt><var>os</var></tt>, is one of:
7226 <tt>linux</tt>, <tt>gnu</tt>, <tt>freebsd</tt> and
7227 <tt>openbsd</tt>. Use of <tt>gnu</tt> in this string is
7228 reserved for the GNU/Hurd operating system.
7233 Note that we don't want to use
7234 <tt><var>arch</var>-debian-linux</tt> to apply to the rule
7235 <tt><var>architecture</var>-<var>vendor</var>-<var>os</var></tt>
7236 since this would make our programs incompatible with other
7237 Linux distributions. We also don't use something like
7238 <tt><var>arch</var>-unknown-linux</tt>, since the
7239 <tt>unknown</tt> does not look very good.
7244 <heading>Daemons</heading>
7247 The configuration files <file>/etc/services</file>,
7248 <file>/etc/protocols</file>, and <file>/etc/rpc</file> are managed
7249 by the <prgn>netbase</prgn> package and must not be modified
7254 If a package requires a new entry in one of these files, the
7255 maintainer should get in contact with the
7256 <prgn>netbase</prgn> maintainer, who will add the entries
7257 and release a new version of the <prgn>netbase</prgn>
7262 The configuration file <file>/etc/inetd.conf</file> must not be
7263 modified by the package's scripts except via the
7264 <prgn>update-inetd</prgn> script or the
7265 <file>DebianNet.pm</file> Perl module. See their documentation
7266 for details on how to add entries.
7270 If a package wants to install an example entry into
7271 <file>/etc/inetd.conf</file>, the entry must be preceded with
7272 exactly one hash character (<tt>#</tt>). Such lines are
7273 treated as "commented out by user" by the
7274 <prgn>update-inetd</prgn> script and are not changed or
7275 activated during package updates.
7280 <heading>Using pseudo-ttys and modifying wtmp, utmp and
7284 Some programs need to create pseudo-ttys. This should be done
7285 using Unix98 ptys if the C library supports it. The resulting
7286 program must not be installed setuid root, unless that
7287 is required for other functionality.
7291 The files <file>/var/run/utmp</file>, <file>/var/log/wtmp</file> and
7292 <file>/var/log/lastlog</file> must be installed writeable by
7293 group <tt>utmp</tt>. Programs which need to modify those
7294 files must be installed setgid <tt>utmp</tt>.
7299 <heading>Editors and pagers</heading>
7302 Some programs have the ability to launch an editor or pager
7303 program to edit or display a text document. Since there are
7304 lots of different editors and pagers available in the Debian
7305 distribution, the system administrator and each user should
7306 have the possibility to choose his/her preferred editor and
7311 In addition, every program should choose a good default
7312 editor/pager if none is selected by the user or system
7317 Thus, every program that launches an editor or pager must
7318 use the EDITOR or PAGER environment variable to determine
7319 the editor or pager the user wishes to use. If these
7320 variables are not set, the programs <file>/usr/bin/editor</file>
7321 and <file>/usr/bin/pager</file> should be used, respectively.
7325 These two files are managed through the <prgn>dpkg</prgn>
7326 "alternatives" mechanism. Thus every package providing an
7327 editor or pager must call the
7328 <prgn>update-alternatives</prgn> script to register these
7333 If it is very hard to adapt a program to make use of the
7334 EDITOR or PAGER variables, that program may be configured to
7335 use <file>/usr/bin/sensible-editor</file> and
7336 <file>/usr/bin/sensible-pager</file> as the editor or pager
7337 program respectively. These are two scripts provided in the
7338 Debian base system that check the EDITOR and PAGER variables
7339 and launch the appropriate program, and fall back to
7340 <file>/usr/bin/editor</file> and <file>/usr/bin/pager</file> if the
7341 variable is not set.
7345 A program may also use the VISUAL environment variable to
7346 determine the user's choice of editor. If it exists, it
7347 should take precedence over EDITOR. This is in fact what
7348 <file>/usr/bin/sensible-editor</file> does.
7352 It is not required for a package to depend on
7353 <tt>editor</tt> and <tt>pager</tt>, nor is it required for a
7354 package to provide such virtual packages.<footnote>
7355 The Debian base system already provides an editor and a
7361 <sect id="web-appl">
7362 <heading>Web servers and applications</heading>
7365 This section describes the locations and URLs that should
7366 be used by all web servers and web applications in the
7373 Cgi-bin executable files are installed in the
7375 <example compact="compact">
7376 /usr/lib/cgi-bin/<var>cgi-bin-name</var>
7378 and should be referred to as
7379 <example compact="compact">
7380 http://localhost/cgi-bin/<var>cgi-bin-name</var>
7385 <p>Access to HTML documents</p>
7388 HTML documents for a package are stored in
7389 <file>/usr/share/doc/<var>package</var></file>
7390 and can be referred to as
7391 <example compact="compact">
7392 http://localhost/doc/<var>package</var>/<var>filename</var>
7397 The web server should restrict access to the document
7398 tree so that only clients on the same host can read
7399 the documents. If the web server does not support such
7400 access controls, then it should not provide access at
7401 all, or ask about providing access during installation.
7406 <p>Web Document Root</p>
7409 Web Applications should try to avoid storing files in
7410 the Web Document Root. Instead they should use the
7411 /usr/share/doc/<var>package</var> directory for
7412 documents and register the Web Application via the
7413 menu package. If access to the web document root is
7414 unavoidable then use
7415 <example compact="compact">
7418 as the Document Root. This might be just a symbolic
7419 link to the location where the system administrator
7420 has put the real document root.
7428 <sect id="mail-transport-agents">
7429 <heading>Mail transport, delivery and user agents</heading>
7432 Debian packages which process electronic mail, whether mail
7433 user agents (MUAs) or mail transport agents (MTAs), must
7434 ensure that they are compatible with the configuration
7435 decisions below. Failure to do this may result in lost
7436 mail, broken <tt>From:</tt> lines, and other serious brain
7441 The mail spool is <file>/var/mail</file> and the interface to
7442 send a mail message is <file>/usr/sbin/sendmail</file> (as per
7443 the FHS). On older systems, the mail spool may be
7444 physically located in <file>/var/spool/mail</file>, but all
7445 access to the mail spool should be via the
7446 <file>/var/mail</file> symlink. The mail spool is part of the
7447 base system and not part of the MTA package.
7451 All Debian MUAs, MTAs, MDAs and other mailbox accessing
7452 programs (such as IMAP daemons) must lock the mailbox in an
7453 NFS-safe way. This means that <tt>fcntl()</tt> locking must
7454 be combined with dot locking. To avoid deadlocks, a program
7455 should use <tt>fcntl()</tt> first and dot locking after
7456 this, or alternatively implement the two locking methods in
7457 a non blocking way<footnote>
7458 If it is not possible to establish both locks, the
7459 system shouldn't wait for the second lock to be
7460 established, but remove the first lock, wait a (random)
7461 time, and start over locking again.
7462 </footnote>. Using the functions <tt>maillock</tt> and
7463 <tt>mailunlock</tt> provided by the
7464 <tt>liblockfile*</tt><footnote>
7465 You will need to depend on <tt>liblockfile1 (>>1.01)</tt>
7466 to use these functions.
7467 </footnote> packages is the recommended way to realize this.
7471 Mailboxes are generally mode 660
7472 <tt><var>user</var>.mail</tt> unless the system
7473 administrator has chosen otherwise. A MUA may remove a
7474 mailbox (unless it has nonstandard permissions) in which
7475 case the MTA or another MUA must recreate it if needed.
7476 Mailboxes must be writable by group mail.
7480 The mail spool is 2775 <tt>root.mail</tt>, and MUAs should
7481 be setgid mail to do the locking mentioned above (and
7482 must obviously avoid accessing other users' mailboxes
7483 using this privilege).</p>
7486 <file>/etc/aliases</file> is the source file for the system mail
7487 aliases (e.g., postmaster, usenet, etc.), it is the one
7488 which the sysadmin and <prgn>postinst</prgn> scripts may
7489 edit. After <file>/etc/aliases</file> is edited the program or
7490 human editing it must call <prgn>newaliases</prgn>. All MTA
7491 packages must come with a <prgn>newaliases</prgn> program,
7492 even if it does nothing, but older MTA packages did not do
7493 this so programs should not fail if <prgn>newaliases</prgn>
7494 cannot be found. Note that because of this, all MTA
7495 packages must have <tt>Provides</tt>, <tt>Conflicts</tt> and
7496 <tt>Replaces: mail-transport-agent</tt> control file
7501 The convention of writing <tt>forward to
7502 <var>address</var></tt> in the mailbox itself is not
7503 supported. Use a <tt>.forward</tt> file instead.</p>
7506 The <prgn>rmail</prgn> program used by UUCP
7507 for incoming mail should be <file>/usr/sbin/rmail</file>.
7508 Likewise, <prgn>rsmtp</prgn>, for receiving
7509 batch-SMTP-over-UUCP, should be <file>/usr/sbin/rsmtp</file> if it
7513 If your package needs to know what hostname to use on (for
7514 example) outgoing news and mail messages which are generated
7515 locally, you should use the file <file>/etc/mailname</file>. It
7516 will contain the portion after the username and <tt>@</tt>
7517 (at) sign for email addresses of users on the machine
7518 (followed by a newline).
7522 Such package should check for the existence of this file
7523 when it is being configured. If it exists, it should be
7524 used without comment, although an MTA's configuration script
7525 may wish to prompt the user even if it finds that this file
7526 exists. If the file does not exist, the package should
7527 prompt the user for the value (preferably using
7528 <prgn>debconf</prgn>) and store it in <file>/etc/mailname</file>
7529 as well as using it in the package's configuration. The
7530 prompt should make it clear that the name will not just be
7531 used by that package. For example, in this situation the
7532 <tt>inn</tt> package could say something like:
7533 <example compact="compact">
7534 Please enter the "mail name" of your system. This is the
7535 hostname portion of the address to be shown on outgoing
7536 news and mail messages. The default is
7537 <var>syshostname</var>, your system's host name. Mail
7538 name ["<var>syshostname</var>"]:
7540 where <var>syshostname</var> is the output of <tt>hostname
7546 <heading>News system configuration</heading>
7549 All the configuration files related to the NNTP (news)
7550 servers and clients should be located under
7551 <file>/etc/news</file>.</p>
7554 There are some configuration issues that apply to a number
7555 of news clients and server packages on the machine. These
7559 <tag><file>/etc/news/organization</file></tag>
7561 A string which should appear as the
7562 organization header for all messages posted
7563 by NNTP clients on the machine
7566 <tag><file>/etc/news/server</file></tag>
7568 Contains the FQDN of the upstream NNTP
7569 server, or localhost if the local machine is
7574 Other global files may be added as required for cross-package news
7581 <heading>Programs for the X Window System</heading>
7584 <heading>Providing X support and package priorities</heading>
7587 Programs that can be configured with support for the X
7588 Window System must be configured to do so and must declare
7589 any package dependencies necessary to satisfy their
7590 runtime requirements when using the X Window System. If
7591 such a package is of higher priority than the X packages
7592 on which it depends, it is required that either the
7593 X-specific components be split into a separate package, or
7594 that an alternative version of the package, which includes
7595 X support, be provided, or that the package's priority be
7601 <heading>Packages providing an X server</heading>
7604 Packages that provide an X server that, directly or
7605 indirectly, communicates with real input and display
7606 hardware should declare in their control data that they
7607 provide the virtual package <tt>xserver</tt>.<footnote>
7608 This implements current practice, and provides an
7609 actual policy for usage of the <tt>xserver</tt>
7610 virtual package which appears in the virtual packages
7611 list. In a nutshell, X servers that interface
7612 directly with the display and input hardware or via
7613 another subsystem (e.g., GGI) should provide
7614 <tt>xserver</tt>. Things like <tt>Xvfb</tt>,
7615 <tt>Xnest</tt>, and <tt>Xprt</tt> should not.
7621 <heading>Packages providing a terminal emulator</heading>
7624 Packages that provide a terminal emulator for the X Window
7625 System which meet the criteria listed below should declare
7626 in their control data that they provide the virtual
7627 package <tt>x-terminal-emulator</tt>. They should also
7628 register themselves as an alternative for
7629 <file>/usr/bin/x-terminal-emulator</file>, with a priority of
7634 To be an <tt>x-terminal-emulator</tt>, a program must:
7635 <list compact="compact">
7637 Be able to emulate a DEC VT100 terminal, or a
7638 compatible terminal.
7642 Support the command-line option <tt>-e
7643 <var>command</var></tt>, which creates a new
7644 terminal window<footnote>
7645 "New terminal window" does not necessarily mean
7646 a new top-level X window directly parented by
7647 the window manager; it could, if the terminal
7648 emulator application were so coded, be a new
7649 "view" in a multiple-document interface (MDI).
7651 and runs the specified <var>command</var>,
7652 interpreting the entirity of the rest of the command
7653 line as a command to pass straight to exec, in the
7654 manner that <tt>xterm</tt> does.
7658 Support the command-line option <tt>-T
7659 <var>title</var></tt>, which creates a new terminal
7660 window with the window title <var>title</var>.
7667 <heading>Packages providing a window manager</heading>
7670 Packages that provide a window manager should declare in
7671 their control data that they provide the virtual package
7672 <tt>x-window-manager</tt>. They should also register
7673 themselves as an alternative for
7674 <file>/usr/bin/x-window-manager</file>, with a priority
7675 calculated as follows:
7676 <list compact="compact">
7678 Start with a priority of 20.
7682 If the window manager supports the Debian menu
7683 system, add 20 points if this support is available
7684 in the package's default configuration (i.e., no
7685 configuration files belonging to the system or user
7686 have to be edited to activate the feature); if
7687 configuration files must be modified, add only 10
7693 If the window manager complies with <url
7694 id="http://www.freedesktop.org/standards/wm-spec.html"
7695 name="The Window Manager Specification Project">,
7696 written by the <url id="http://www.freedesktop.org/"
7697 name="Free Desktop Group">, add 40 points.
7701 If the window manager permits the X session to be
7702 restarted using a <em>different</em> window manager
7703 (without killing the X server) in its default
7704 configuration, add 10 points; otherwise add none.
7711 <heading>Packages providing fonts</heading>
7714 Packages that provide fonts for the X Window
7716 For the purposes of Debian Policy, a "font for the X
7717 Window System" is one which is accessed via X protocol
7718 requests. Fonts for the Linux console, for PostScript
7719 renderers, or any other purpose, do not fit this
7720 definition. Any tool which makes such fonts available
7721 to the X Window System, however, must abide by this
7724 must do a number of things to ensure that they are both
7725 available without modification of the X or font server
7726 configuration, and that they do not corrupt files used by
7727 other font packages to register information about
7731 Fonts of any type supported by the X Window System
7732 must be in a separate binary package from any
7733 executables, libraries, or documentation (except
7734 that specific to the fonts shipped, such as their
7735 license information). If one or more of the fonts
7736 so packaged are necessary for proper operation of
7737 the package with which they are associated the font
7738 package may be Recommended; if the fonts merely
7739 provide an enhancement, a Suggests relationship may
7740 be used. Packages must not Depend on font
7742 This is because the X server may retrieve fonts
7743 from the local filesystem or over the network
7744 from an X font server; the Debian package system
7745 is empowered to deal only with the local
7751 BDF fonts must be converted to PCF fonts with the
7752 <prgn>bdftopcf</prgn> utility (available in the
7753 <tt>xutils</tt> package, <prgn>gzip</prgn>ped, and
7754 placed in a directory that corresponds to their
7756 <list compact="compact">
7758 100 dpi fonts must be placed in
7759 <file>/usr/X11R6/lib/X11/fonts/100dpi/</file>.
7763 75 dpi fonts must be placed in
7764 <file>/usr/X11R6/lib/X11/fonts/75dpi/</file>.
7768 Character-cell fonts, cursor fonts, and other
7769 low-resolution fonts must be placed in
7770 <file>/usr/X11R6/lib/X11/fonts/misc/</file>.
7776 Speedo fonts must be placed in
7777 <file>/usr/X11R6/lib/X11/fonts/Speedo/</file>.
7781 Type 1 fonts must be placed in
7782 <file>/usr/X11R6/lib/X11/fonts/Type1/</file>. If font
7783 metric files are available, they must be placed here
7788 Subdirectories of <file>/usr/X11R6/lib/X11/fonts/</file>
7789 other than those listed above must be neither
7790 created nor used. (The <file>PEX</file>, <file>CID</file>,
7791 and <file>cyrillic</file> directories are excepted for
7792 historical reasons, but installation of files into
7793 these directories remains discouraged.)
7797 Font packages may, instead of placing files directly
7798 in the X font directories listed above, provide
7799 symbolic links in that font directory pointing to
7800 the files' actual location in the filesystem. Such
7801 a location must comply with the FHS.
7805 Font packages should not contain both 75dpi and
7806 100dpi versions of a font. If both are available,
7807 they should be provided in separate binary packages
7808 with <tt>-75dpi</tt> or <tt>-100dpi</tt> appended to
7809 the names of the packages containing the
7810 corresponding fonts.
7814 Fonts destined for the <file>misc</file> subdirectory
7815 should not be included in the same package as 75dpi
7816 or 100dpi fonts; instead, they should be provided in
7817 a separate package with <tt>-misc</tt> appended to
7822 Font packages must not provide the files
7823 <file>fonts.dir</file>, <file>fonts.alias</file>, or
7824 <file>fonts.scale</file> in a font directory:
7827 <file>fonts.dir</file> files must not be provided at all.
7831 <file>fonts.alias</file> and <file>fonts.scale</file>
7832 files, if needed, should be provided in the
7834 <file>/etc/X11/fonts/<var>fontdir</var>/<var>package</var>.<var>extension</var></file>,
7835 where <var>fontdir</var> is the name of the
7837 <file>/usr/X11R6/lib/X11/fonts/</file> where the
7838 package's corresponding fonts are stored
7839 (e.g., <tt>75dpi</tt> or <tt>misc</tt>),
7840 <var>package</var> is the name of the package
7841 that provides these fonts, and
7842 <var>extension</var> is either <tt>scale</tt>
7843 or <tt>alias</tt>, whichever corresponds to
7850 Font packages must declare a dependency on
7851 <tt>xutils (>> 4.0.3)</tt> in their control
7856 Font packages that provide one or more
7857 <file>fonts.scale</file> files as described above must
7858 invoke <prgn>update-fonts-scale</prgn> on each
7859 directory into which they installed fonts
7860 <em>before</em> invoking
7861 <prgn>update-fonts-dir</prgn> on that directory.
7862 This invocation must occur in both the
7863 <prgn>postinst</prgn> (for all arguments) and
7864 <prgn>postrm</prgn> (for all arguments except
7865 <tt>upgrade</tt>) scripts.
7869 Font packages that provide one or more
7870 <file>fonts.alias</file> files as described above must
7871 invoke <prgn>update-fonts-alias</prgn> on each
7872 directory into which they installed fonts. This
7873 invocation must occur in both the
7874 <prgn>postinst</prgn> (for all arguments) and
7875 <prgn>postrm</prgn> (for all arguments except
7876 <tt>upgrade</tt>) scripts.
7880 Font packages must invoke
7881 <prgn>update-fonts-dir</prgn> on each directory into
7882 which they installed fonts. This invocation must
7883 occur in both the <prgn>postinst</prgn> (for all
7884 arguments) and <prgn>postrm</prgn> (for all
7885 arguments except <tt>upgrade</tt>) scripts.
7889 Font packages must not provide alias names for the
7890 fonts they include which collide with alias names
7891 already in use by fonts already packaged.
7895 Font packages must not provide fonts with the same
7896 XLFD registry name as another font already packaged.
7903 <heading>Application defaults files</heading>
7906 Application defaults files must be installed in the
7907 directory <file>/etc/X11/app-defaults/</file> (use of a
7908 localized subdirectory of <file>/etc/X11/</file> as described
7909 in the <em>X Toolkit Intrinsics - C Language
7910 Interface</em> manual is also permitted). They must be
7911 registered as <tt>conffile</tt>s or handled as
7912 configuration files. Packages must not provide the
7913 directory <file>/usr/X11R6/lib/X11/app-defaults/</file>.
7917 Customization of programs' X resources may also be
7918 supported with the provision of a file with the same name
7919 as that of the package placed in the
7920 <file>/etc/X11/Xresources/</file> directory, which must
7921 registered as a <tt>conffile</tt> or handled as a
7922 configuration file.<footnote>
7923 Note that this mechanism is not the same as using
7924 app-defaults; app-defaults are tied to the client
7925 binary on the local filesystem, whereas X resources
7926 are stored in the X server and affect all connecting
7929 <em>Important:</em> packages that install files into the
7930 <file>/etc/X11/Xresources/</file> directory must conflict with
7931 <tt>xbase (<< 3.3.2.3a-2)</tt>; if this is not done
7932 it is possible for the installing package to destroy a
7933 previously-existing <file>/etc/X11/Xresources</file> file
7934 which had been customized by the system administrator.
7939 <heading>Installation directory issues</heading>
7942 Packages using the X Window System should not be
7943 configured to install files under the <file>/usr/X11R6/</file>
7944 directory unless they use <prgn>imake</prgn>. The
7945 <file>/usr/X11R6/</file> directory hierarchy should be
7946 regarded as deprecated for all packages except the X
7947 Window System itself, and those which use the
7948 <prgn>imake</prgn> program it provides, in which case the
7949 packages may transition out of the <file>/usr/X11R6/</file>
7950 directory at the maintainer's discretion.<footnote>
7951 <prgn>Imake</prgn>-using programs are exempt because,
7952 as long as they are written correctly, the pathnames
7953 they use to locate resources and install themselves
7954 are derived wholly from the X Window System
7955 configuration. Thus, in the event that the X Window
7956 System moves to <file>/usr/X11R7/</file>,
7957 <file>/usr/X12/</file>, or just plain <file>/usr/</file>, all
7958 that is required for these programs is a recompile
7959 against the corresponding X Window System library
7960 development packages.
7965 Programs that use GNU <prgn>autoconf</prgn> and
7966 <prgn>automake</prgn> are usually easily configured at
7967 compile time to use <file>/usr/</file> instead of
7968 <file>/usr/X11R6/</file>, and this should be done whenever
7969 possible. Configuration files for window managers and
7970 display managers should be placed in a subdirectory of
7971 <file>/etc/X11/</file> corresponding to the package name due
7972 to these programs' tight integration with the mechanisms
7973 of the X Window System. Application-level programs should
7974 use the <file>/etc/</file> directory unless otherwise mandated
7979 The installation of files into subdirectories
7980 of <file>/usr/X11R6/include/X11/</file> and
7981 <file>/usr/X11R6/lib/X11/</file> is permitted but discouraged;
7982 package maintainers should determine if subdirectories of
7983 <file>/usr/lib/</file> and <file>/usr/share/</file> can be used
7984 instead. (The use of symbolic links from the
7985 <file>X11R6</file> directories to other FHS-compliant
7986 locations is encouraged if the program is not easily
7987 configured to look elsewhere for its files.)
7991 Packages must not provide or install files into the directories
7992 <file>/usr/bin/X11/</file>, <file>/usr/include/X11/</file> or
7993 <file>/usr/lib/X11/</file>. Files within a package should,
7994 however, make reference to these directories, rather than
7995 their <tt>X11R6</tt>-named counterparts
7996 <file>/usr/X11R6/bin/</file>, <file>/usr/X11R6/include/X11/</file>
7997 and <file>/usr/X11R6/lib/X11/</file>, if the resources being
7998 referred to have not been moved to other FHS-compliant
8004 <heading>The OSF/Motif and OpenMotif libraries</heading>
8007 <em>Programs that require the non-DFSG-compliant OSF/Motif or
8008 OpenMotif libraries</em><footnote>
8009 OSF/Motif and OpenMotif are collectively referred to as
8010 "Motif" in this policy document.
8012 should be compiled against and tested with LessTif (a free
8013 re-implementation of Motif) instead. If the maintainer
8014 judges that the program or programs do not work
8015 sufficiently well with LessTif to be distributed and
8016 supported, but do so when compiled against Motif, then two
8017 versions of the package should be created; one linked
8018 statically against Motif and with <tt>-smotif</tt>
8019 appended to the package name, and one linked dynamically
8020 against Motif and with <tt>-dmotif</tt> appended to the
8025 Both Motif-linked versions are dependent
8026 upon non-DFSG-compliant software and thus cannot be
8027 uploaded to the <em>main</em> distribution; if the
8028 software is itself DFSG-compliant it may be uploaded to
8029 the <em>contrib</em> distribution. While known existing
8030 versions of Motif permit unlimited redistribution of
8031 binaries linked against the library (whether statically or
8032 dynamically), it is the package maintainer's
8033 responsibility to determine whether this is permitted by
8034 the license of the copy of Motif in his or her possession.
8040 <heading>Perl programs and modules</heading>
8043 Perl programs and modules should follow the current Perl policy.
8047 The Perl policy can be found in the <tt>perl-policy</tt>
8048 files in the <tt>debian-policy</tt> package.
8049 It is also available from the Debian web mirrors at
8050 <tt><url name="/doc/packaging-manuals/perl-policy/"
8051 id="http://www.debian.org/doc/packaging-manuals/perl-policy/"></tt>
8052 and from the Debian archive mirrors at
8053 <tt><url name="/doc/package-developer/perl-policy.txt.gz"
8054 id="http://ftp.debian.org/debian/doc/package-developer/perl-policy.txt.gz"></tt>.
8059 <heading>Emacs lisp programs</heading>
8062 Please refer to the "Debian Emacs Policy" for details of how to
8063 package emacs lisp programs.
8067 The Emacs policy is available in
8068 <file>debian-emacs-policy.gz</file> of the
8069 <package>emacsen-common</package> package.
8070 It is also available from the Debian web mirrors at
8071 <tt><url name="/doc/packaging-manuals/debian-emacs-policy"
8072 id="http://www.debian.org/doc/packaging-manuals/debian-emacs-policy"></tt>.
8077 <heading>Games</heading>
8080 The permissions on <file>/var/games</file> are mode 755, owner
8081 <tt>root</tt> and group <tt>root</tt>.
8085 Each game decides on its own security policy.</p>
8088 Games which require protected, privileged access to
8089 high-score files, savegames, etc., may be made
8090 set-<em>group</em>-id (mode 2755) and owned by
8091 <tt>root.games</tt>, and use files and directories with
8092 appropriate permissions (770 <tt>root.games</tt>, for
8093 example). They must not be made
8094 set-<em>user</em>-id, as this causes security problems. (If
8095 an attacker can subvert any set-user-id game they can
8096 overwrite the executable of any other, causing other players
8097 of these games to run a Trojan horse program. With a
8098 set-group-id game the attacker only gets access to less
8099 important game data, and if they can get at the other
8100 players' accounts at all it will take considerably more
8104 Some packages, for example some fortune cookie programs, are
8105 configured by the upstream authors to install with their
8106 data files or other static information made unreadable so
8107 that they can only be accessed through set-id programs
8108 provided. You should not do this in a Debian package: anyone can
8109 download the <file>.deb</file> file and read the data from it,
8110 so there is no point making the files unreadable. Not
8111 making the files unreadable also means that you don't have
8112 to make so many programs set-id, which reduces the risk of a
8116 As described in the FHS, binaries of games should be
8117 installed in the directory <file>/usr/games</file>. This also
8118 applies to games that use the X Window System. Manual pages
8119 for games (X and non-X games) should be installed in
8120 <file>/usr/share/man/man6</file>.</p>
8126 <heading>Documentation</heading>
8129 <heading>Manual pages</heading>
8132 You should install manual pages in <prgn>nroff</prgn> source
8133 form, in appropriate places under <file>/usr/share/man</file>.
8134 You should only use sections 1 to 9 (see the FHS for more
8135 details). You must not install a preformatted "cat page".
8139 Each program, utility, and function should have an
8140 associated manual page included in the same package. It is
8141 suggested that all configuration files also have a manual
8142 page included as well. Manual pages for protocols and other
8143 auxiliary things are optional.
8147 If no manual page is available, this is considered as a bug
8148 and should be reported to the Debian Bug Tracking System (the
8149 maintainer of the package is allowed to write this bug report
8150 themselves, if they so desire). Do not close the bug report
8151 until a proper manpage is available.<footnote>
8152 It is not very hard to write a man page. See the
8153 <url id="http://www.schweikhardt.net/man_page_howto.html"
8154 name="Man-Page-HOWTO">,
8155 <manref name="man" section="7">, the examples
8156 created by <prgn>debmake</prgn> or <prgn>dh_make</prgn>,
8157 the helper programs <prgn>help2man</prgn>, or the
8158 directory <file>/usr/share/doc/man-db/examples</file>.
8163 You may forward a complaint about a missing manpage to the
8164 upstream authors, and mark the bug as forwarded in the
8165 Debian bug tracking system. Even though the GNU Project do
8166 not in general consider the lack of a manpage to be a bug,
8167 we do; if they tell you that they don't consider it a bug
8168 you should leave the bug in our bug tracking system open
8173 Manual pages should be installed compressed using <tt>gzip -9</tt>.
8177 If one manpage needs to be accessible via several names it
8178 is better to use a symbolic link than the <file>.so</file>
8179 feature, but there is no need to fiddle with the relevant
8180 parts of the upstream source to change from <file>.so</file> to
8181 symlinks: don't do it unless it's easy. You should not
8182 create hard links in the manual page directories, nor put
8183 absolute filenames in <file>.so</file> directives. The filename
8184 in a <file>.so</file> in a manpage should be relative to the
8185 base of the manpage tree (usually
8186 <file>/usr/share/man</file>). If you do not create any links
8187 (whether symlinks, hard links, or <tt>.so</tt> directives)
8188 in the filesystem to the alternate names of the manpage,
8189 then you should not rely on <prgn>man</prgn> finding your
8190 manpage under those names based solely on the information in
8191 the manpage's header.<footnote>
8192 Supporting this in <prgn>man</prgn> often requires
8193 unreasonable processing time to find a manual page or to
8194 report that none exists, and moves knowledge into man's
8195 database that would be better left in the filesystem.
8196 This support is therefore deprecated and will cease to
8197 be present in the future.
8203 <heading>Info documents</heading>
8206 Info documents should be installed in <file>/usr/share/info</file>.
8207 They should be compressed with <tt>gzip -9</tt>.
8211 Your package should call <prgn>install-info</prgn> to update
8212 the Info <file>dir</file> file in its <prgn>postinst</prgn>
8213 script when called with a <tt>configure</tt> argument, for
8215 <example compact="compact">
8216 install-info --quiet --section Development Development \
8217 /usr/share/info/foobar.info
8221 It is a good idea to specify a section for the location of
8222 your program; this is done with the <tt>--section</tt>
8223 switch. To determine which section to use, you should look
8224 at <file>/usr/share/info/dir</file> on your system and choose the most
8225 relevant (or create a new section if none of the current
8226 sections are relevant). Note that the <tt>--section</tt>
8227 flag takes two arguments; the first is a regular expression
8228 to match (case-insensitively) against an existing section,
8229 the second is used when creating a new one.</p>
8232 You should remove the entries in the <prgn>prerm</prgn>
8233 script when called with a <tt>remove</tt> argument:
8234 <example compact="compact">
8235 install-info --quiet --remove /usr/share/info/foobar.info
8239 If <prgn>install-info</prgn> cannot find a description entry
8240 in the Info file you must supply one. See <manref
8241 name="install-info" section="8"> for details.</p>
8245 <heading>Additional documentation</heading>
8248 Any additional documentation that comes with the package may
8249 be installed at the discretion of the package maintainer.
8250 Text documentation should be installed in the directory
8251 <file>/usr/share/doc/<var>package</var></file>, where
8252 <var>package</var> is the name of the package, and
8253 compressed with <tt>gzip -9</tt> unless it is small.
8257 If a package comes with large amounts of documentation which
8258 many users of the package will not require you should create
8259 a separate binary package to contain it, so that it does not
8260 take up disk space on the machines of users who do not need
8261 or want it installed.</p>
8264 It is often a good idea to put text information files
8265 (<file>README</file>s, changelogs, and so forth) that come with
8266 the source package in <file>/usr/share/doc/<var>package</var></file>
8267 in the binary package. However, you don't need to install
8268 the instructions for building and installing the package, of
8272 Packages must not require the existence of any files in
8273 <file>/usr/share/doc/</file> in order to function
8275 The system administrator should be able to
8276 delete files in <file>/usr/share/doc/</file> without causing
8277 any programs to break.
8279 Any files that are referenced by programs but are also
8280 useful as standalone documentation should be installed under
8281 <file>/usr/share/<var>package</var>/</file> with symbolic links from
8282 <file>/usr/share/doc/<var>package</var></file>.
8286 <file>/usr/share/doc/<var>package</var></file> may be a symbolic
8287 link to another directory in <file>/usr/share/doc</file> only if
8288 the two packages both come from the same source and the
8289 first package Depends on the second.
8293 Former Debian releases placed all additional documentation
8294 in <file>/usr/doc/<var>package</var></file>. This has been
8295 changed to <file>/usr/share/doc/<var>package</var></file>,
8296 and packages must not put documentation in the directory
8297 <file>/usr/doc/<var>package</var></file>. <footnote>
8298 At this phase of the transition, we no longer require a
8299 symbolic link in <file>/usr/doc/</file>. At a later point,
8300 policy shall change to make the symbolic links a bug.
8306 <heading>Preferred documentation formats</heading>
8309 The unification of Debian documentation is being carried out
8313 If your package comes with extensive documentation in a
8314 markup format that can be converted to various other formats
8315 you should if possible ship HTML versions in a binary
8316 package, in the directory
8317 <file>/usr/share/doc/<var>appropriate-package</var></file> or
8318 its subdirectories.<footnote>
8319 The rationale: The important thing here is that HTML
8320 docs should be available in <em>some</em> package, not
8321 necessarily in the main binary package.
8326 Other formats such as PostScript may be provided at the
8327 package maintainer's discretion.
8331 <sect id="copyrightfile">
8332 <heading>Copyright information</heading>
8335 Every package must be accompanied by a verbatim copy of its
8336 copyright and distribution license in the file
8337 <file>/usr/share/doc/<var>package</var>/copyright</file>. This
8338 file must neither be compressed nor be a symbolic link.
8342 In addition, the copyright file must say where the upstream
8343 sources (if any) were obtained. It should name the original
8344 authors of the package and the Debian maintainer(s) who were
8345 involved with its creation.</p>
8348 A copy of the file which will be installed in
8349 <file>/usr/share/doc/<var>package</var>/copyright</file> should
8350 be in <file>debian/copyright</file> in the source package.
8354 <file>/usr/share/doc/<var>package</var></file> may be a symbolic
8355 link to another directory in <file>/usr/share/doc</file> only if
8356 the two packages both come from the same source and the
8357 first package Depends on the second. These rules are
8358 important because copyrights must be extractable by
8363 Packages distributed under the UCB BSD license, the Artistic
8364 license, the GNU GPL, and the GNU LGPL should refer to the
8365 files <file>/usr/share/common-licenses/BSD</file>,
8366 <file>/usr/share/common-licenses/Artistic</file>,
8367 <file>/usr/share/common-licenses/GPL</file>, and
8368 <file>/usr/share/common-licenses/LGPL</file> respectively,
8369 rather than quoting them in the copyright file.
8373 You should not use the copyright file as a general <file>README</file>
8374 file. If your package has such a file it should be
8375 installed in <file>/usr/share/doc/<var>package</var>/README</file> or
8376 <file>README.Debian</file> or some other appropriate place.</p>
8380 <heading>Examples</heading>
8383 Any examples (configurations, source files, whatever),
8384 should be installed in a directory
8385 <file>/usr/share/doc/<var>package</var>/examples</file>. These
8386 files should not be referenced by any program: they're there
8387 for the benefit of the system administrator and users as
8388 documentation only. Architecture-specific example files
8389 should be installed in a directory
8390 <file>/usr/lib/<var>package</var>/examples</file> with symbolic
8392 <file>/usr/share/doc/<var>package</var>/examples</file>, or the
8393 latter directory itself may be a symbolic link to the
8398 If the purpose of a package is to provide examples, then the
8399 example files may be installed into
8400 <file>/usr/share/doc/<var>package</var></file>.
8404 <sect id="changelogs">
8405 <heading>Changelog files</heading>
8408 Packages that are not Debian-native must contain a
8409 compressed copy of the <file>debian/changelog</file> file from
8410 the Debian source tree in
8411 <file>/usr/share/doc/<var>package</var></file> with the name
8412 <file>changelog.Debian.gz</file>.
8416 If an upstream changelog is available, it should be accessible as
8417 <file>/usr/share/doc/<var>package</var>/changelog.gz</file> in
8418 plain text. If the upstream changelog is distributed in
8419 HTML, it should be made available in that form as
8420 <file>/usr/share/doc/<var>package</var>/changelog.html.gz</file>
8421 and a plain text <file>changelog.gz</file> should be generated
8422 from it using, for example, <tt>lynx -dump -nolist</tt>. If
8423 the upstream changelog files do not already conform to this
8424 naming convention, then this may be achieved either by
8425 renaming the files, or by adding a symbolic link, at the
8426 maintainer's discretion.<footnote>
8427 Rationale: People should not have to look in places for
8428 upstream changelogs merely because they are given
8429 different names or are distributed in HTML format.
8434 All of these files should be installed compressed using
8435 <tt>gzip -9</tt>, as they will become large with time even
8436 if they start out small.
8440 If the package has only one changelog which is used both as
8441 the Debian changelog and the upstream one because there is
8442 no separate upstream maintainer then that changelog should
8443 usually be installed as
8444 <file>/usr/share/doc/<var>package</var>/changelog.gz</file>; if
8445 there is a separate upstream maintainer, but no upstream
8446 changelog, then the Debian changelog should still be called
8447 <file>changelog.Debian.gz</file>.
8451 For details about the format and contents of the Debian
8452 changelog file, please see <ref id="dpkgchangelog">.
8457 <appendix id="pkg-scope">
8458 <heading>Introduction and scope of these appendices</heading>
8461 These appendices are taken essentially verbatim from the
8462 now-deprecated Packaging Manual, version 3.2.1.0. They are
8463 the chapters which are likely to be of use to package
8464 maintainers and which have not already been included in the
8465 policy document itself. Most of these sections are very likely
8466 not relevant to policy; they should be treated as
8467 documentation for the packaging system. Please note that these
8468 appendices are included for convenience, and for historical
8469 reasons: they used to be part of policy package, and they have
8470 not yet been incorporated into dpkg documentation. However,
8471 they still have value, and hence they are presented here.
8475 They have not yet been checked to ensure that they are
8476 compatible with the contents of policy, and if there are any
8477 contradictions, the version in the main policy document takes
8478 precedence. The remaining chapters of the old Packaging
8479 Manual have also not been read in detail to ensure that there
8480 are not parts which have been left out. Both of these will be
8485 Certain parts of the Packaging manual were integrated into the
8486 Policy Manual proper, and removed from the appendices. Links
8487 have been placed from the old locations to the new ones.
8491 <prgn>dpkg</prgn> is a suite of programs for creating binary
8492 package files and installing and removing them on Unix
8494 <prgn>dpkg</prgn> is targetted primarily at Debian
8495 GNU/Linux, but may work on or be ported to other
8501 The binary packages are designed for the management of
8502 installed executable programs (usually compiled binaries) and
8503 their associated data, though source code examples and
8504 documentation are provided as part of some packages.</p>
8507 This manual describes the technical aspects of creating Debian
8508 binary packages (<file>.deb</file> files). It documents the
8509 behaviour of the package management programs
8510 <prgn>dpkg</prgn>, <prgn>dselect</prgn> et al. and the way
8511 they interact with packages.</p>
8514 It also documents the interaction between
8515 <prgn>dselect</prgn>'s core and the access method scripts it
8516 uses to actually install the selected packages, and describes
8517 how to create a new access method.</p>
8520 This manual does not go into detail about the options and
8521 usage of the package building and installation tools. It
8522 should therefore be read in conjuction with those programs'
8527 The utility programs which are provided with <prgn>dpkg</prgn>
8528 for managing various system configuration and similar issues,
8529 such as <prgn>update-rc.d</prgn> and
8530 <prgn>install-info</prgn>, are not described in detail here -
8531 please see their manpages.
8535 It is assumed that the reader is reasonably familiar with the
8536 <prgn>dpkg</prgn> System Administrators' manual.
8537 Unfortunately this manual does not yet exist.
8541 The Debian version of the FSF's GNU hello program is provided
8542 as an example for people wishing to create Debian
8543 packages. The Debian <prgn>debmake</prgn> package is
8544 recommended as a very helpful tool in creating and maintaining
8545 Debian packages. However, while the tools and examples are
8546 helpful, they do not replace the need to read and follow the
8547 Policy and Programmer's Manual.</p>
8550 <appendix id="pkg-binarypkg">
8551 <heading>Binary packages (from old Packaging Manual)</heading>
8554 The binary package has two main sections. The first part
8555 consists of various control information files and scripts used
8556 by <prgn>dpkg</prgn> when installing and removing. See <ref
8557 id="pkg-controlarea">.
8561 The second part is an archive containing the files and
8562 directories to be installed.
8566 In the future binary packages may also contain other
8567 components, such as checksums and digital signatures. The
8568 format for the archive is described in full in the
8569 <file>deb(5)</file> manpage.
8573 <sect id="pkg-bincreating"><heading>Creating package files -
8574 <prgn>dpkg-deb</prgn>
8578 All manipulation of binary package files is done by
8579 <prgn>dpkg-deb</prgn>; it's the only program that has
8580 knowledge of the format. (<prgn>dpkg-deb</prgn> may be
8581 invoked by calling <prgn>dpkg</prgn>, as <prgn>dpkg</prgn>
8582 will spot that the options requested are appropriate to
8583 <prgn>dpkg-deb</prgn> and invoke that instead with the same
8588 In order to create a binary package you must make a
8589 directory tree which contains all the files and directories
8590 you want to have in the filesystem data part of the package.
8591 In Debian-format source packages this directory is usually
8592 <file>debian/tmp</file>, relative to the top of the package's
8597 They should have the locations (relative to the root of the
8598 directory tree you're constructing) ownerships and
8599 permissions which you want them to have on the system when
8604 With current versions of <prgn>dpkg</prgn> the uid/username
8605 and gid/groupname mappings for the users and groups being
8606 used should be the same on the system where the package is
8607 built and the one where it is installed.
8611 You need to add one special directory to the root of the
8612 miniature filesystem tree you're creating:
8613 <prgn>DEBIAN</prgn>. It should contain the control
8614 information files, notably the binary package control file
8615 (see <ref id="pkg-controlfile">).
8619 The <prgn>DEBIAN</prgn> directory will not appear in the
8620 filesystem archive of the package, and so won't be installed
8621 by <prgn>dpkg</prgn> when the package is installed.
8625 When you've prepared the package, you should invoke:
8627 dpkg --build <var>directory</var>
8632 This will build the package in
8633 <file><var>directory</var>.deb</file>. (<prgn>dpkg</prgn> knows
8634 that <tt>--build</tt> is a <prgn>dpkg-deb</prgn> option, so
8635 it invokes <prgn>dpkg-deb</prgn> with the same arguments to
8640 See the manpage <manref name="dpkg-deb" section="8"> for details of how
8641 to examine the contents of this newly-created file. You may find the
8642 output of following commands enlightening:
8644 dpkg-deb --info <var>filename</var>.deb
8645 dpkg-deb --contents <var>filename</var>.deb
8646 dpkg --contents <var>filename</var>.deb
8648 To view the copyright file for a package you could use this command:
8650 dpkg --fsys-tarfile <var>filename</var>.deb | tar xof usr/share/doc/<var>\*</var>copyright | less
8655 <sect id="pkg-controlarea">
8656 <heading>Package control information files</heading>
8659 The control information portion of a binary package is a
8660 collection of files with names known to <prgn>dpkg</prgn>.
8661 It will treat the contents of these files specially - some
8662 of them contain information used by <prgn>dpkg</prgn> when
8663 installing or removing the package; others are scripts which
8664 the package maintainer wants <prgn>dpkg</prgn> to run.
8668 It is possible to put other files in the package control
8669 area, but this is not generally a good idea (though they
8670 will largely be ignored).
8674 Here is a brief list of the control info files supported by
8675 <prgn>dpkg</prgn> and a summary of what they're used for.
8680 <tag><tt>control</tt>
8683 This is the key description file used by
8684 <prgn>dpkg</prgn>. It specifies the package's name
8685 and version, gives its description for the user,
8686 states its relationships with other packages, and so
8687 forth. See <ref id="sourcecontrolfiles"> and
8688 <ref id="binarycontrolfiles">.
8692 It is usually generated automatically from information
8693 in the source package by the
8694 <prgn>dpkg-gencontrol</prgn> program, and with
8695 assistance from <prgn>dpkg-shlibdeps</prgn>.
8696 See <ref id="pkg-sourcetools">.
8700 <tag><tt>postinst</tt>, <tt>preinst</tt>, <tt>postrm</tt>,
8705 These are exectuable files (usually scripts) which
8706 <prgn>dpkg</prgn> runs during installation, upgrade
8707 and removal of packages. They allow the package to
8708 deal with matters which are particular to that package
8709 or require more complicated processing than that
8710 provided by <prgn>dpkg</prgn>. Details of when and
8711 how they are called are in <ref id="maintainerscripts">.
8715 It is very important to make these scripts idempotent.
8716 See <ref id="idempotency">.
8720 The maintainer scripts are guaranteed to run with a
8721 controlling terminal and can interact with the user.
8722 See <ref id="controllingterminal">.
8726 <tag><tt>conffiles</tt>
8729 This file contains a list of configuration files which
8730 are to be handled automatically by <prgn>dpkg</prgn>
8731 (see <ref id="pkg-conffiles">). Note that not necessarily
8732 every configuration file should be listed here.
8735 <tag><tt>shlibs</tt>
8738 This file contains a list of the shared libraries
8739 supplied by the package, with dependency details for
8740 each. This is used by <prgn>dpkg-shlibdeps</prgn>
8741 when it determines what dependencies are required in a
8742 package control file. The <tt>shlibs</tt> file format
8743 is described on <ref id="shlibs">.
8748 <sect id="pkg-controlfile">
8749 <heading>The main control information file: <tt>control</tt></heading>
8752 The most important control information file used by
8753 <prgn>dpkg</prgn> when it installs a package is
8754 <tt>control</tt>. It contains all the package's "vital
8759 The binary package control files of packages built from
8760 Debian sources are made by a special tool,
8761 <prgn>dpkg-gencontrol</prgn>, which reads
8762 <file>debian/control</file> and <file>debian/changelog</file> to
8763 find the information it needs. See <ref id="pkg-sourcepkg"> for
8768 The fields in binary package control files are listed in
8769 <ref id="binarycontrolfiles">.
8773 A description of the syntax of control files and the purpose
8774 of the fields is available in <ref id="controlfields">.
8779 <heading>Time Stamps</heading>
8782 See <ref id="timestamps">.
8787 <appendix id="pkg-sourcepkg">
8788 <heading>Source packages (from old Packaging Manual) </heading>
8791 The Debian binary packages in the distribution are generated
8792 from Debian sources, which are in a special format to assist
8793 the easy and automatic building of binaries.
8796 <sect id="pkg-sourcetools">
8797 <heading>Tools for processing source packages</heading>
8800 Various tools are provided for manipulating source packages;
8801 they pack and unpack sources and help build of binary
8802 packages and help manage the distribution of new versions.
8806 They are introduced and typical uses described here; see
8807 <manref name="dpkg-source" section="1"> for full
8808 documentation about their arguments and operation.
8812 For examples of how to construct a Debian source package,
8813 and how to use those utilities that are used by Debian
8814 source packages, please see the <prgn>hello</prgn> example
8820 <prgn>dpkg-source</prgn> - packs and unpacks Debian source
8825 This program is frequently used by hand, and is also
8826 called from package-independent automated building scripts
8827 such as <prgn>dpkg-buildpackage</prgn>.
8831 To unpack a package it is typically invoked with
8833 dpkg-source -x <var>.../path/to/filename</var>.dsc
8838 with the <file><var>filename</var>.tar.gz</file> and
8839 <file><var>filename</var>.diff.gz</file> (if applicable) in
8840 the same directory. It unpacks into
8841 <file><var>package</var>-<var>version</var></file>, and if
8843 <file><var>package</var>-<var>version</var>.orig</file>, in
8844 the current directory.
8848 To create a packed source archive it is typically invoked:
8850 dpkg-source -b <var>package</var>-<var>version</var>
8855 This will create the <file>.dsc</file>, <file>.tar.gz</file> and
8856 <file>.diff.gz</file> (if appropriate) in the current
8857 directory. <prgn>dpkg-source</prgn> does not clean the
8858 source tree first - this must be done separately if it is
8863 See also <ref id="pkg-sourcearchives">.</p>
8869 <prgn>dpkg-buildpackage</prgn> - overall package-building
8874 <prgn>dpkg-buildpackage</prgn> is a script which invokes
8875 <prgn>dpkg-source</prgn>, the <file>debian/rules</file>
8876 targets <tt>clean</tt>, <tt>build</tt> and
8877 <tt>binary</tt>, <prgn>dpkg-genchanges</prgn> and
8878 <prgn>pgp</prgn> to build a signed source and binary
8883 It is usually invoked by hand from the top level of the
8884 built or unbuilt source directory. It may be invoked with
8885 no arguments; useful arguments include:
8886 <taglist compact="compact">
8887 <tag><tt>-uc</tt>, <tt>-us</tt></tag>
8890 Do not PGP-sign the <tt>.changes</tt> file or the
8891 source package <tt>.dsc</tt> file, respectively.</p>
8893 <tag><tt>-p<var>pgp-command</var></tt></tag>
8896 Invoke <var>pgp-command</var> instead of finding
8897 <tt>pgp</tt> on the <prgn>PATH</prgn>.
8898 <var>pgp-command</var> must behave just like
8899 <prgn>pgp</prgn>.</p>
8901 <tag><tt>-r<var>root-command</var></tt></tag>
8904 When root privilege is required, invoke the command
8905 <var>root-command</var>. <var>root-command</var>
8906 should invoke its first argument as a command, from
8907 the <prgn>PATH</prgn> if necessary, and pass its
8908 second and subsequent arguments to the command it
8909 calls. If no <var>root-command</var> is supplied
8910 then <var>dpkg-buildpackage</var> will take no
8911 special action to gain root privilege, so that for
8912 most packages it will have to be invoked as root to
8915 <tag><tt>-b</tt>, <tt>-B</tt></tag>
8918 Two types of binary-only build and upload - see
8919 <manref name="dpkg-source" section="1">.
8928 <prgn>dpkg-gencontrol</prgn> - generates binary package
8933 This program is usually called from <file>debian/rules</file>
8934 (see <ref id="pkg-sourcetree">) in the top level of the source
8939 This is usually done just before the files and directories in the
8940 temporary directory tree where the package is being built have their
8941 permissions and ownerships set and the package is constructed using
8942 <prgn>dpkg-deb/</prgn>
8944 This is so that the control file which is produced has
8945 the right permissions
8950 <prgn>dpkg-gencontrol</prgn> must be called after all the
8951 files which are to go into the package have been placed in
8952 the temporary build directory, so that its calculation of
8953 the installed size of a package is correct.
8957 It is also necessary for <prgn>dpkg-gencontrol</prgn> to
8958 be run after <prgn>dpkg-shlibdeps</prgn> so that the
8959 variable substitutions created by
8960 <prgn>dpkg-shlibdeps</prgn> in <file>debian/substvars</file>
8965 For a package which generates only one binary package, and
8966 which builds it in <file>debian/tmp</file> relative to the top
8967 of the source package, it is usually sufficient to call
8968 <prgn>dpkg-gencontrol</prgn>.
8972 Sources which build several binaries will typically need
8975 dpkg-gencontrol -Pdebian/tmp-<var>pkg</var> -p<var>package</var>
8976 </example> The <tt>-P</tt> tells
8977 <prgn>dpkg-gencontrol</prgn> that the package is being
8978 built in a non-default directory, and the <tt>-p</tt>
8979 tells it which package's control file should be generated.
8983 <prgn>dpkg-gencontrol</prgn> also adds information to the
8984 list of files in <file>debian/files</file>, for the benefit of
8985 (for example) a future invocation of
8986 <prgn>dpkg-genchanges</prgn>.</p>
8991 <prgn>dpkg-shlibdeps</prgn> - calculates shared library
8996 This program is usually called from <file>debian/rules</file>
8997 just before <prgn>dpkg-gencontrol</prgn> (see <ref
8998 id="pkg-sourcetree">), in the top level of the source tree.
9002 Its arguments are executables.
9005 In a forthcoming dpkg version,
9006 <prgn>dpkg-shlibdeps</prgn> would be required to be
9007 called on shared libraries as well.
9010 They may be specified either in the locations in the
9011 source tree where they are created or in the locations
9012 in the temporary build tree where they are installed
9013 prior to binary package creation.
9015 </footnote> for which shared library dependencies should
9016 be included in the binary package's control file.
9020 If some of the found shared libraries should only
9021 warrant a <tt>Recommends</tt> or <tt>Suggests</tt>, or if
9022 some warrant a <tt>Pre-Depends</tt>, this can be achieved
9023 by using the <tt>-d<var>dependency-field</var></tt> option
9024 before those executable(s). (Each <tt>-d</tt> option
9025 takes effect until the next <tt>-d</tt>.)
9029 <prgn>dpkg-shlibdeps</prgn> does not directly cause the
9030 output control file to be modified. Instead by default it
9031 adds to the <file>debian/substvars</file> file variable
9032 settings like <tt>shlibs:Depends</tt>. These variable
9033 settings must be referenced in dependency fields in the
9034 appropriate per-binary-package sections of the source
9039 For example, the <prgn>procps</prgn> package generates two
9040 kinds of binaries, simple C binaries like <prgn>ps</prgn>
9041 which require a predependency and full-screen ncurses
9042 binaries like <prgn>top</prgn> which require only a
9043 recommendation. It can say in its <file>debian/rules</file>:
9045 dpkg-shlibdeps -dPre-Depends ps -dRecommends top
9047 and then in its main control file <file>debian/control</file>:
9051 Pre-Depends: ${shlibs:Pre-Depends}
9052 Recommends: ${shlibs:Recommends}
9058 Sources which produce several binary packages with
9059 different shared library dependency requirements can use
9060 the <tt>-p<var>varnameprefix</var></tt> option to override
9061 the default <tt>shlibs:</tt> prefix (one invocation of
9062 <prgn>dpkg-shlibdeps</prgn> per setting of this option).
9063 They can thus produce several sets of dependency
9064 variables, each of the form
9065 <tt><var>varnameprefix</var>:<var>dependencyfield</var></tt>,
9066 which can be referred to in the appropriate parts of the
9067 binary package control files.
9074 <prgn>dpkg-distaddfile</prgn> - adds a file to
9075 <file>debian/files</file>
9079 Some packages' uploads need to include files other than
9080 the source and binary package files.
9084 <prgn>dpkg-distaddfile</prgn> adds a file to the
9085 <file>debian/files</file> file so that it will be included in
9086 the <file>.changes</file> file when
9087 <prgn>dpkg-genchanges</prgn> is run.
9091 It is usually invoked from the <tt>binary</tt> target of
9092 <file>debian/rules</file>:
9094 dpkg-distaddfile <var>filename</var> <var>section</var> <var>priority</var>
9096 The <var>filename</var> is relative to the directory where
9097 <prgn>dpkg-genchanges</prgn> will expect to find it - this
9098 is usually the directory above the top level of the source
9099 tree. The <file>debian/rules</file> target should put the
9100 file there just before or just after calling
9101 <prgn>dpkg-distaddfile</prgn>.
9105 The <var>section</var> and <var>priority</var> are passed
9106 unchanged into the resulting <file>.changes</file> file.
9111 <sect1><heading><prgn>dpkg-genchanges</prgn> - generates a <file>.changes</file> upload
9116 This program is usually called by package-independent
9117 automatic building scripts such as
9118 <prgn>dpkg-buildpackage</prgn>, but it may also be called
9123 It is usually called in the top level of a built source
9124 tree, and when invoked with no arguments will print out a
9125 straightforward <file>.changes</file> file based on the
9126 information in the source package's changelog and control
9127 file and the binary and source packages which should have
9133 <sect1><heading><prgn>dpkg-parsechangelog</prgn> - produces parsed representation of
9138 This program is used internally by
9139 <prgn>dpkg-source</prgn> et al. It may also occasionally
9140 be useful in <file>debian/rules</file> and elsewhere. It
9141 parses a changelog, <file>debian/changelog</file> by default,
9142 and prints a control-file format representation of the
9143 information in it to standard output.
9147 <sect1 id="pkg-dpkgarch"><heading><prgn>dpkg-architecture</prgn> -
9148 information about the build and host system
9152 This program can be used manually, but is also invoked by
9153 <tt>dpkg-buildpackage</tt> or <file>debian/rules</file> to set
9154 to set environment or make variables which specify the build and
9155 host architecture for the package building process.
9160 <sect id="pkg-sourcetree">
9161 <heading>The Debianised source tree</heading>
9164 The source archive scheme described later is intended to
9165 allow a Debianised source tree with some associated control
9166 information to be reproduced and transported easily. The
9167 Debianised source tree is a version of the original program
9168 with certain files added for the benefit of the
9169 Debianisation process, and with any other changes required
9170 made to the rest of the source code and installation
9175 The extra files created for Debian are in the subdirectory
9176 <file>debian</file> of the top level of the Debianised source
9177 tree. They are described below.
9180 <sect1 id="pkg-debianrules">
9181 <heading><file>debian/rules</file> - the main building script</heading>
9184 See <ref id="debianrules">.
9189 <sect1 id="pkg-dpkgchangelog">
9190 <heading><file>debian/changelog</file></heading>
9193 See <ref id="dpkgchangelog">.
9197 It is recommended that the entire changelog be encoded in the
9198 <url id="http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2279.html" name="UTF-8">
9200 <url id="http://www.unicode.org/"
9201 name="Unicode">.<footnote>
9203 Support for Unicode, and specifically UTF-8, is
9204 steadily increasing among popular applications in
9205 Debian. For example, in unstable, GNOME 2 has
9206 excellent support (almost level 2) in almost all its
9207 applications; the big remaining one is gnome-terminal,
9208 of which one requires development versions in order to
9209 support UTF-8 (available in Debian experimental now if
9210 you want to play). I think that by the time sarge is
9211 released, UTF-8 support will start to hit critical
9214 I think it is fairly obvious that we need to
9215 eventually transition to UTF-8 for our package
9216 infrastructure; it is really the only sane charset in
9217 an international environment. Now, we can't switch to
9218 using UTF-8 for package control fields and the like
9219 until dpkg has better support, but one thing we can
9220 start doing today is requesting that Debian changelogs
9221 are UTF-8 encoded. At some point in time, we can start
9222 requiring them to do so.
9225 Checking for non-UTF8 characters in a changelog is
9226 trivial. Dump the file through
9227 <example>iconv -f utf-8 -t ucs-4</example>
9228 discard the output, and check the return
9229 value. If there are any characters in the stream
9230 which are invalid UTF-8 sequences, iconv will exit
9231 with an error code; and this will be the case for the
9232 vast majority of other character sets.
9237 <sect2><heading>Defining alternative changelog formats
9241 It is possible to use a different format to the standard
9242 one, by providing a parser for the format you wish to
9247 In order to have <tt>dpkg-parsechangelog</tt> run your
9248 parser, you must include a line within the last 40 lines
9249 of your file matching the Perl regular expression:
9250 <tt>\schangelog-format:\s+([0-9a-z]+)\W</tt> The part in
9251 parentheses should be the name of the format. For
9252 example, you might say:
9254 @@@ changelog-format: joebloggs @@@
9256 Changelog format names are non-empty strings of alphanumerics.
9260 If such a line exists then <tt>dpkg-parsechangelog</tt>
9261 will look for the parser as
9262 <file>/usr/lib/dpkg/parsechangelog/<var>format-name</var></file>
9264 <file>/usr/local/lib/dpkg/parsechangelog/<var>format-name</var></file>;
9265 it is an error for it not to find it, or for it not to
9266 be an executable program. The default changelog format
9267 is <tt>dpkg</tt>, and a parser for it is provided with
9268 the <tt>dpkg</tt> package.
9272 The parser will be invoked with the changelog open on
9273 standard input at the start of the file. It should read
9274 the file (it may seek if it wishes) to determine the
9275 information required and return the parsed information
9276 to standard output in the form of a series of control
9277 fields in the standard format. By default it should
9278 return information about only the most recent version in
9279 the changelog; it should accept a
9280 <tt>-v<var>version</var></tt> option to return changes
9281 information from all versions present <em>strictly
9282 after</em> <var>version</var>, and it should then be an
9283 error for <var>version</var> not to be present in the
9289 <list compact="compact">
9290 <item><qref id="f-Source"><tt>Source</tt></qref></item>
9291 <item><qref id="f-Version"><tt>Version</tt></qref> (mandatory)</item>
9292 <item><qref id="f-Distribution"><tt>Distribution</tt></qref> (mandatory)</item>
9293 <item><qref id="f-Urgency"><tt>Urgency</tt></qref> (mandatory)</item>
9294 <item><qref id="f-Maintainer"><tt>Maintainer</tt></qref> (mandatory)</item>
9295 <item><qref id="f-Date"><tt>Date</tt></qref></item>
9296 <item><qref id="f-Changes"><tt>Changes</tt></qref> (mandatory)</item>
9301 If several versions are being returned (due to the use
9302 of <tt>-v</tt>), the urgency value should be of the
9303 highest urgency code listed at the start of any of the
9304 versions requested followed by the concatenated
9305 (space-separated) comments from all the versions
9306 requested; the maintainer, version, distribution and
9307 date should always be from the most recent version.
9311 For the format of the <tt>Changes</tt> field see
9312 <ref id="f-Changes">.
9316 If the changelog format which is being parsed always or
9317 almost always leaves a blank line between individual
9318 change notes these blank lines should be stripped out,
9319 so as to make the resulting output compact.
9323 If the changelog format does not contain date or package
9324 name information this information should be omitted from
9325 the output. The parser should not attempt to synthesise
9326 it or find it from other sources.
9330 If the changelog does not have the expected format the
9331 parser should exit with a nonzero exit status, rather
9332 than trying to muddle through and possibly generating
9337 A changelog parser may not interact with the user at
9343 <sect1 id="pkg-srcsubstvars">
9344 <heading><file>debian/substvars</file> and variable substitutions</heading>
9347 See <ref id="substvars">.
9353 <heading><file>debian/files</file></heading>
9356 See <ref id="debianfiles">.
9360 <sect1><heading><file>debian/tmp</file>
9364 This is the canonical temporary location for the
9365 construction of binary packages by the <tt>binary</tt>
9366 target. The directory <file>tmp</file> serves as the root of
9367 the filesystem tree as it is being constructed (for
9368 example, by using the package's upstream makefiles install
9369 targets and redirecting the output there), and it also
9370 contains the <tt>DEBIAN</tt> subdirectory. See <ref
9371 id="pkg-bincreating">.
9375 If several binary packages are generated from the same
9376 source tree it is usual to use several
9377 <file>debian/tmp<var>something</var></file> directories, for
9378 example <file>tmp-a</file> or <file>tmp-doc</file>.
9382 Whatever <file>tmp</file> directories are created and used by
9383 <tt>binary</tt> must of course be removed by the
9384 <tt>clean</tt> target.</p></sect1>
9388 <sect id="pkg-sourcearchives"><heading>Source packages as archives
9392 As it exists on the FTP site, a Debian source package
9393 consists of three related files. You must have the right
9394 versions of all three to be able to use them.
9399 <tag>Debian source control file - <tt>.dsc</tt></tag>
9401 This file is a control file used by <prgn>dpkg-source</prgn>
9402 to extract a source package.
9403 See <ref id="debiansourcecontrolfiles">.
9407 Original source archive -
9409 <var>package</var>_<var>upstream-version</var>.orig.tar.gz
9416 This is a compressed (with <tt>gzip -9</tt>)
9417 <prgn>tar</prgn> file containing the source code from
9418 the upstream authors of the program. The tarfile
9419 unpacks into a directory
9420 <file><var>package</var>-<var>upstream-version</var>.orig</file>,
9421 and does not contain files anywhere other than in
9422 there or in its subdirectories.</p>
9426 Debianisation diff -
9428 <var>package</var>_<var>upstream_version-revision</var>.diff.gz
9434 This is a unified context diff (<tt>diff -u</tt>)
9435 giving the changes which are required to turn the
9436 original source into the Debian source. These changes
9437 may only include editing and creating plain files.
9438 The permissions of files, the targets of symbolic
9439 links and the characteristics of special files or
9440 pipes may not be changed and no files may be removed
9445 All the directories in the diff must exist, except the
9446 <file>debian</file> subdirectory of the top of the source
9447 tree, which will be created by
9448 <prgn>dpkg-source</prgn> if necessary when unpacking.
9452 The <prgn>dpkg-source</prgn> program will
9453 automatically make the <file>debian/rules</file> file
9454 executable (see below).</p></item>
9459 If there is no original source code - for example, if the
9460 package is specially prepared for Debian or the Debian
9461 maintainer is the same as the upstream maintainer - the
9462 format is slightly different: then there is no diff, and the
9464 <file><var>package</var>_<var>version</var>.tar.gz</file> and
9465 contains a directory
9466 <file><var>package</var>-<var>version</var></file>.
9471 <heading>Unpacking a Debian source package without <prgn>dpkg-source</prgn></heading>
9474 <tt>dpkg-source -x</tt> is the recommended way to unpack a
9475 Debian source package. However, if it is not available it
9476 is possible to unpack a Debian source archive as follows:
9477 <enumlist compact="compact">
9480 Untar the tarfile, which will create a <file>.orig</file>
9484 <p>Rename the <file>.orig</file> directory to
9485 <file><var>package</var>-<var>version</var></file>.</p>
9489 Create the subdirectory <file>debian</file> at the top of
9490 the source tree.</p>
9492 <item><p>Apply the diff using <tt>patch -p0</tt>.</p>
9494 <item><p>Untar the tarfile again if you want a copy of the original
9495 source code alongside the Debianised version.</p>
9500 It is not possible to generate a valid Debian source archive
9501 without using <prgn>dpkg-source</prgn>. In particular,
9502 attempting to use <prgn>diff</prgn> directly to generate the
9503 <file>.diff.gz</file> file will not work.
9507 <heading>Restrictions on objects in source packages</heading>
9510 The source package may not contain any hard links
9512 This is not currently detected when building source
9513 packages, but only when extracting
9517 Hard links may be permitted at some point in the
9518 future, but would require a fair amount of
9520 </footnote>, device special files, sockets or setuid or
9523 Setgid directories are allowed.
9528 The source packaging tools manage the changes between the
9529 original and Debianised source using <prgn>diff</prgn> and
9530 <prgn>patch</prgn>. Turning the original source tree as
9531 included in the <file>.orig.tar.gz</file> into the debianised
9532 source must not involve any changes which cannot be
9533 handled by these tools. Problematic changes which cause
9534 <prgn>dpkg-source</prgn> to halt with an error when
9535 building the source package are:
9536 <list compact="compact">
9537 <item><p>Adding or removing symbolic links, sockets or pipes.</p>
9539 <item><p>Changing the targets of symbolic links.</p>
9541 <item><p>Creating directories, other than <file>debian</file>.</p>
9543 <item><p>Changes to the contents of binary files.</p></item>
9544 </list> Changes which cause <prgn>dpkg-source</prgn> to
9545 print a warning but continue anyway are:
9546 <list compact="compact">
9549 Removing files, directories or symlinks.
9551 Renaming a file is not treated specially - it is
9552 seen as the removal of the old file (which
9553 generates a warning, but is otherwise ignored),
9554 and the creation of the new one.
9560 Changed text files which are missing the usual final
9561 newline (either in the original or the modified
9566 Changes which are not represented, but which are not detected by
9567 <prgn>dpkg-source</prgn>, are:
9568 <list compact="compact">
9569 <item><p>Changing the permissions of files (other than
9570 <file>debian/rules</file>) and directories.</p></item>
9575 The <file>debian</file> directory and <file>debian/rules</file>
9576 are handled specially by <prgn>dpkg-source</prgn> - before
9577 applying the changes it will create the <file>debian</file>
9578 directory, and afterwards it will make
9579 <file>debian/rules</file> world-exectuable.
9585 <appendix id="pkg-controlfields">
9586 <heading>Control files and their fields (from old Packaging Manual)</heading>
9589 Many of the tools in the <prgn>dpkg</prgn> suite manipulate
9590 data in a common format, known as control files. Binary and
9591 source packages have control data as do the <file>.changes</file>
9592 files which control the installation of uploaded files, and
9593 <prgn>dpkg</prgn>'s internal databases are in a similar
9598 <heading>Syntax of control files</heading>
9601 See <ref id="controlsyntax">.
9605 It is important to note that there are several fields which
9606 are optional as far as <prgn>dpkg</prgn> and the related
9607 tools are concerned, but which must appear in every Debian
9608 package, or whose omission may cause problems.
9613 <heading>List of fields</heading>
9616 See <ref id="controlfieldslist">.
9620 This section now contains only the fields that didn't belong
9621 to the Policy manual.
9624 <sect1 id="pkg-f-Filename">
9625 <heading><tt>Filename</tt> and <tt>MSDOS-Filename</tt></heading>
9628 These fields in <tt>Packages</tt> files give the
9629 filename(s) of (the parts of) a package in the
9630 distribution directories, relative to the root of the
9631 Debian hierarchy. If the package has been split into
9632 several parts the parts are all listed in order, separated
9637 <sect1 id="pkg-f-Size">
9638 <heading><tt>Size</tt> and <tt>MD5sum</tt></heading>
9641 These fields in <file>Packages</file> files give the size (in
9642 bytes, expressed in decimal) and MD5 checksum of the
9643 file(s) which make(s) up a binary package in the
9644 distribution. If the package is split into several parts
9645 the values for the parts are listed in order, separated by
9650 <sect1 id="pkg-f-Status">
9651 <heading><tt>Status</tt></heading>
9654 This field in <prgn>dpkg</prgn>'s status file records
9655 whether the user wants a package installed, removed or
9656 left alone, whether it is broken (requiring
9657 reinstallation) or not and what its current state on the
9658 system is. Each of these pieces of information is a
9663 <sect1 id="pkg-f-Config-Version">
9664 <heading><tt>Config-Version</tt></heading>
9667 If a package is not installed or not configured, this
9668 field in <prgn>dpkg</prgn>'s status file records the last
9669 version of the package which was successfully
9674 <sect1 id="pkg-f-Conffiles">
9675 <heading><tt>Conffiles</tt></heading>
9678 This field in <prgn>dpkg</prgn>'s status file contains
9679 information about the automatically-managed configuration
9680 files held by a package. This field should <em>not</em>
9681 appear anywhere in a package!
9686 <heading>Obsolete fields</heading>
9689 These are still recognised by <prgn>dpkg</prgn> but should
9690 not appear anywhere any more.
9692 <taglist compact="compact">
9694 <tag><tt>Revision</tt></tag>
9695 <tag><tt>Package-Revision</tt></tag>
9696 <tag><tt>Package_Revision</tt></tag>
9698 The Debian revision part of the package version was
9699 at one point in a separate control file field. This
9700 field went through several names.
9703 <tag><tt>Recommended</tt></tag>
9704 <item>Old name for <tt>Recommends</tt>.</item>
9706 <tag><tt>Optional</tt></tag>
9707 <item>Old name for <tt>Suggests</tt>.</item>
9709 <tag><tt>Class</tt></tag>
9710 <item>Old name for <tt>Priority</tt>.</item>
9719 <appendix id="pkg-conffiles">
9720 <heading>Configuration file handling (from old Packaging Manual)</heading>
9723 <prgn>dpkg</prgn> can do a certain amount of automatic
9724 handling of package configuration files.
9728 Whether this mechanism is appropriate depends on a number of
9729 factors, but basically there are two approaches to any
9730 particular configuration file.
9734 The easy method is to ship a best-effort configuration in the
9735 package, and use <prgn>dpkg</prgn>'s conffile mechanism to
9736 handle updates. If the user is unlikely to want to edit the
9737 file, but you need them to be able to without losing their
9738 changes, and a new package with a changed version of the file
9739 is only released infrequently, this is a good approach.
9743 The hard method is to build the configuration file from
9744 scratch in the <prgn>postinst</prgn> script, and to take the
9745 responsibility for fixing any mistakes made in earlier
9746 versions of the package automatically. This will be
9747 appropriate if the file is likely to need to be different on
9751 <sect><heading>Automatic handling of configuration files by
9756 A package may contain a control area file called
9757 <tt>conffiles</tt>. This file should be a list of filenames
9758 of configuration files needing automatic handling, separated
9759 by newlines. The filenames should be absolute pathnames,
9760 and the files referred to should actually exist in the
9765 When a package is upgraded <prgn>dpkg</prgn> will process
9766 the configuration files during the configuration stage,
9767 shortly before it runs the package's <prgn>postinst</prgn>
9772 For each file it checks to see whether the version of the
9773 file included in the package is the same as the one that was
9774 included in the last version of the package (the one that is
9775 being upgraded from); it also compares the version currently
9776 installed on the system with the one shipped with the last
9781 If neither the user nor the package maintainer has changed
9782 the file, it is left alone. If one or the other has changed
9783 their version, then the changed version is preferred - i.e.,
9784 if the user edits their file, but the package maintainer
9785 doesn't ship a different version, the user's changes will
9786 stay, silently, but if the maintainer ships a new version
9787 and the user hasn't edited it the new version will be
9788 installed (with an informative message). If both have
9789 changed their version the user is prompted about the problem
9790 and must resolve the differences themselves.
9794 The comparisons are done by calculating the MD5 message
9795 digests of the files, and storing the MD5 of the file as it
9796 was included in the most recent version of the package.
9800 When a package is installed for the first time
9801 <prgn>dpkg</prgn> will install the file that comes with it,
9802 unless that would mean overwriting a file already on the
9807 However, note that <prgn>dpkg</prgn> will <em>not</em>
9808 replace a conffile that was removed by the user (or by a
9809 script). This is necessary because with some programs a
9810 missing file produces an effect hard or impossible to
9811 achieve in another way, so that a missing file needs to be
9812 kept that way if the user did it.
9816 Note that a package should <em>not</em> modify a
9817 <prgn>dpkg</prgn>-handled conffile in its maintainer
9818 scripts. Doing this will lead to <prgn>dpkg</prgn> giving
9819 the user confusing and possibly dangerous options for
9820 conffile update when the package is upgraded.</p>
9823 <sect><heading>Fully-featured maintainer script configuration
9828 For files which contain site-specific information such as
9829 the hostname and networking details and so forth, it is
9830 better to create the file in the package's
9831 <prgn>postinst</prgn> script.
9835 This will typically involve examining the state of the rest
9836 of the system to determine values and other information, and
9837 may involve prompting the user for some information which
9838 can't be obtained some other way.
9842 When using this method there are a couple of important
9843 issues which should be considered:
9847 If you discover a bug in the program which generates the
9848 configuration file, or if the format of the file changes
9849 from one version to the next, you will have to arrange for
9850 the postinst script to do something sensible - usually this
9851 will mean editing the installed configuration file to remove
9852 the problem or change the syntax. You will have to do this
9853 very carefully, since the user may have changed the file,
9854 perhaps to fix the very problem that your script is trying
9855 to deal with - you will have to detect these situations and
9856 deal with them correctly.
9860 If you do go down this route it's probably a good idea to
9861 make the program that generates the configuration file(s) a
9862 separate program in <file>/usr/sbin</file>, by convention called
9863 <file><var>package</var>config</file> and then run that if
9864 appropriate from the post-installation script. The
9865 <tt><var>package</var>config</tt> program should not
9866 unquestioningly overwrite an existing configuration - if its
9867 mode of operation is geared towards setting up a package for
9868 the first time (rather than any arbitrary reconfiguration
9869 later) you should have it check whether the configuration
9870 already exists, and require a <tt>--force</tt> flag to
9871 overwrite it.</p></sect>
9874 <appendix id="pkg-alternatives"><heading>Alternative versions of
9875 an interface - <prgn>update-alternatives</prgn> (from old
9880 When several packages all provide different versions of the
9881 same program or file it is useful to have the system select a
9882 default, but to allow the system administrator to change it
9883 and have their decisions respected.
9887 For example, there are several versions of the <prgn>vi</prgn>
9888 editor, and there is no reason to prevent all of them from
9889 being installed at once, each under their own name
9890 (<prgn>nvi</prgn>, <prgn>vim</prgn> or whatever).
9891 Nevertheless it is desirable to have the name <tt>vi</tt>
9892 refer to something, at least by default.
9896 If all the packages involved cooperate, this can be done with
9897 <prgn>update-alternatives</prgn>.
9901 Each package provides its own version under its own name, and
9902 calls <prgn>update-alternatives</prgn> in its postinst to
9903 register its version (and again in its prerm to deregister
9908 See the manpage <manref name="update-alternatives"
9909 section="8"> for details.
9913 If <prgn>update-alternatives</prgn> does not seem appropriate
9914 you may wish to consider using diversions instead.</p>
9917 <appendix id="pkg-diversions"><heading>Diversions - overriding a
9918 package's version of a file (from old Packaging Manual)
9922 It is possible to have <prgn>dpkg</prgn> not overwrite a file
9923 when it reinstalls the package it belongs to, and to have it
9924 put the file from the package somewhere else instead.
9928 This can be used locally to override a package's version of a
9929 file, or by one package to override another's version (or
9930 provide a wrapper for it).
9934 Before deciding to use a diversion, read <ref
9935 id="pkg-alternatives"> to see if you really want a diversion
9936 rather than several alternative versions of a program.
9940 There is a diversion list, which is read by <prgn>dpkg</prgn>,
9941 and updated by a special program <prgn>dpkg-divert</prgn>.
9942 Please see <manref name="dpkg-divert" section="8"> for full
9943 details of its operation.
9947 When a package wishes to divert a file from another, it should
9948 call <prgn>dpkg-divert</prgn> in its preinst to add the
9949 diversion and rename the existing file. For example,
9950 supposing that a <prgn>smailwrapper</prgn> package wishes to
9951 install a wrapper around <file>/usr/sbin/smail</file>:
9953 if [ install = "$1" ]; then
9954 dpkg-divert --package smailwrapper --add --rename \
9955 --divert /usr/sbin/smail.real /usr/sbin/smail
9957 </example> Testing <tt>$1</tt> is necessary so that the script
9958 doesn't try to add the diversion again when
9959 <prgn>smailwrapper</prgn> is upgraded. The <tt>--package
9960 smailwrapper</tt> ensures that <prgn>smailwrapper</prgn>'s
9961 copy of <file>/usr/sbin/smail</file> can bypass the diversion and
9962 get installed as the true version.
9966 The postrm has to do the reverse:
9968 if [ remove = "$1" ]; then
9969 dpkg-divert --package smailwrapper --remove --rename \
9970 --divert /usr/sbin/smail.real /usr/sbin/smail
9976 Do not attempt to divert a file which is vitally important for
9977 the system's operation - when using <prgn>dpkg-divert</prgn>
9978 there is a time, after it has been diverted but before
9979 <prgn>dpkg</prgn> has installed the new version, when the file
9985 <!-- vim:set ai et sts=2 sw=2 tw=76: -->