# SOME DESCRIPTIVE TITLE. # Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017, # The Debian Policy Mailing List # This file is distributed under the same license as the Debian Policy # Manual package. # FIRST AUTHOR , 2018. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Debian Policy Manual 4.1.6.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-04-07 13:08+0800\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 2.10.3\n" #: ../../ch-binary.rst:2 msgid "Binary packages" msgstr "" #: ../../ch-binary.rst:4 msgid "" "The Debian distribution is based on the Debian package management system," " called ``dpkg``. Thus, all packages in the Debian distribution must be " "provided in the ``.deb`` file format." msgstr "" #: ../../ch-binary.rst:8 msgid "" "A ``.deb`` package contains two sets of files: a set of files to install " "on the system when the package is installed, and a set of files that " "provide additional metadata about the package or which are executed when " "the package is installed or removed. This second set of files is called " "*package metadata files*. Among those files are the package maintainer " "scripts and ``control``, the :ref:`binary package control file " "` that contains the control fields for the package." " Other package metadata files include :ref:`symbols ` or :ref:`shlibs ` used to store shared " "library dependency information and the ``conffiles`` file that lists the " "package's configuration files (described in :ref:`s-config-files`)." msgstr "" #: ../../ch-binary.rst:21 msgid "" "There is unfortunately a collision of terminology here between control " "information files and files in the Debian control file format. Throughout" " this document, a *control file* refers to a file in the Debian control " "file format. These files are documented in :doc:`Control files and their " "fields `. Only files referred to specifically as " "*package metadata files* are the files included in the package metadata " "member (called ``control.tar``) of the ``.deb`` file format used by " "binary packages. Most package metadata files are not in the Debian " "control file format." msgstr "" #: ../../ch-binary.rst:34 msgid "The package name" msgstr "" #: ../../ch-binary.rst:36 msgid "Every package must have a name that's unique within the Debian archive." msgstr "" #: ../../ch-binary.rst:38 msgid "" "The package name is included in the control field ``Package``, the format" " of which is described in :ref:`s-f-Package`. The package name is also " "included as a part of the file name of the ``.deb`` file." msgstr "" #: ../../ch-binary.rst:46 msgid "Packages with potentially offensive content" msgstr "" #: ../../ch-binary.rst:48 msgid "" "As a maintainer you should make a judgement about whether the contents of" " a package is appropriate to include, whether it needs any kind of " "content warning, and whether some parts should be split out into a " "separate package (so that users who want to avoid certain parts can do " "so). In making these decisions you should take into account the " "project's views as expressed in our Diversity Statement." msgstr "" #: ../../ch-binary.rst:55 msgid "" "If you split out (potentially) offensive or disturbing material into a " "separate package, you should usually mark this in the package name by " "adding ``-offensive``. For example, ``cowsay`` vs ``cowsay-offensive``." " In this situation the ``-offensive`` package can be Suggested by the " "core package(s), but should not be Recommended or Depended on." msgstr "" #: ../../ch-binary.rst:65 msgid "The version of a package" msgstr "" #: ../../ch-binary.rst:67 msgid "" "Every package has a version number recorded in its ``Version`` control " "file field, described in :ref:`s-f-Version`." msgstr "" #: ../../ch-binary.rst:70 msgid "" "The package management system imposes an ordering on version numbers, so " "that it can tell whether packages are being up- or downgraded and so that" " package system front end applications can tell whether a package it " "finds available is newer than the one installed on the system. The " "version number format has the most significant parts (as far as " "comparison is concerned) at the beginning." msgstr "" #: ../../ch-binary.rst:77 msgid "" "If an upstream package has problematic version numbers they should be " "converted to a sane form for use in the ``Version`` field." msgstr "" #: ../../ch-binary.rst:83 msgid "Version numbers based on dates" msgstr "" #: ../../ch-binary.rst:85 msgid "" "In general, Debian packages should use the same version numbers as the " "upstream sources. However, upstream version numbers based on some date " "formats (sometimes used for development or \"snapshot\" releases) will " "not be ordered correctly by the package management software. For example," " ``dpkg`` will consider \"96May01\" to be greater than \"96Dec24\"." msgstr "" #: ../../ch-binary.rst:91 msgid "" "To prevent having to use epochs for every new upstream version, the date-" "based portion of any upstream version number should be given in a way " "that sorts correctly: four-digit year first, followed by a two-digit " "numeric month, followed by a two-digit numeric date, possibly with " "punctuation between the components." msgstr "" #: ../../ch-binary.rst:97 msgid "" "Native Debian packages (i.e., packages which have been written especially" " for Debian) whose version numbers include dates should also follow these" " rules. If punctuation is desired between the date components, remember " "that hyphen (``-``) cannot be used in native version numbers. Period " "(``.``) is normally a good choice." msgstr "" #: ../../ch-binary.rst:106 msgid "Uniqueness of version numbers" msgstr "" #: ../../ch-binary.rst:108 msgid "" "The part of the version number after the epoch must not be reused for a " "version of the package with different contents once the package has been " "accepted into the archive, even if the version of the package previously " "using that part of the version number is no longer present in any archive" " suites." msgstr "" #: ../../ch-binary.rst:114 msgid "" "This uniqueness requirement applies to the version numbers of source " "packages and of binary packages, even if the source package producing a " "given binary package changes. Thus the version numbers which a binary " "package must not reuse includes the version numbers of any versions of " "the binary package ever accepted into the archive, under any source " "package." msgstr "" #: ../../ch-binary.rst:121 msgid "" "Additionally, for non-native packages, the upstream version must not be " "reused for different upstream source code, so that for each source " "package name and upstream version number there exists exactly one " "original source archive contents (see :ref:`s-f-Files`)." msgstr "" #: ../../ch-binary.rst:126 msgid "" "The reason for these restrictions is as follows. Epochs are not included" " in the names of the files that compose source packages, or in the " "filenames of binary packages, so reusing a version number, even if the " "epoch differs, results in identically named files with different " "contents. This can cause various problems." msgstr "" #: ../../ch-binary.rst:132 msgid "" "If you find yourself wanting to reuse the part of a version number after " "the epoch, you can just increment the Debian revision, which doesn't need" " to start at 1 or be consecutive." msgstr "" #: ../../ch-binary.rst:139 msgid "The maintainer of a package" msgstr "" #: ../../ch-binary.rst:141 msgid "" "Every package must have a maintainer, except for orphaned packages as " "described below. The maintainer may be one person or a group of people " "reachable from a common email address, such as a mailing list. The " "maintainer is responsible for maintaining the Debian packaging files, " "evaluating and responding appropriately to reported bugs, uploading new " "versions of the package (either directly or through a sponsor), ensuring " "that the package is placed in the appropriate archive area and included " "in Debian releases as appropriate for the stability and utility of the " "package, and requesting removal of the package from the Debian " "distribution if it is no longer useful or maintainable." msgstr "" #: ../../ch-binary.rst:152 msgid "" "The maintainer must be specified in the ``Maintainer`` control field with" " their correct name and a working email address. The email address given " "in the ``Maintainer`` control field must accept mail from those role " "accounts in Debian used to send automated mails regarding the package. " "This includes non-spam mail from the bug-tracking system, all mail from " "the Debian archive maintenance software, and other role accounts or " "automated processes that are commonly agreed on by the project. [#]_ If " "one person or team maintains several packages, they should use the same " "form of their name and email address in the ``Maintainer`` fields of " "those packages." msgstr "" #: ../../ch-binary.rst:163 msgid "" "The format of the ``Maintainer`` control field is described in " ":ref:`s-f-Maintainer`." msgstr "" #: ../../ch-binary.rst:166 msgid "" "If the maintainer of the package is a team of people with a shared email " "address, the ``Uploaders`` control field must be present and must contain" " at least one human with their personal email address. See " ":ref:`s-f-Uploaders` for the syntax of that field." msgstr "" #: ../../ch-binary.rst:171 msgid "" "An orphaned package is one with no current maintainer. Orphaned packages " "should have their ``Maintainer`` control field set to ``Debian QA Group " "``. These packages are considered maintained by " "the Debian project as a whole until someone else volunteers to take over " "maintenance. [#]_" msgstr "" #: ../../ch-binary.rst:179 msgid "The description of a package" msgstr "" #: ../../ch-binary.rst:181 msgid "" "Every Debian package must have a ``Description`` control field which " "contains a synopsis and extended description of the package. Technical " "information about the format of the ``Description`` field is in " ":ref:`s-f-Description`." msgstr "" #: ../../ch-binary.rst:186 msgid "" "The description should describe the package (the program) to a user " "(system administrator) who has never met it before so that they have " "enough information to decide whether they want to install it. This " "description should not just be copied verbatim from the program's " "documentation." msgstr "" #: ../../ch-binary.rst:192 msgid "" "Put important information first, both in the synopsis and extended " "description. Sometimes only the first part of the synopsis or of the " "description will be displayed. You can assume that there will usually be " "a way to see the whole extended description." msgstr "" #: ../../ch-binary.rst:197 msgid "" "The description should also give information about the significant " "dependencies and conflicts between this package and others, so that the " "user knows why these dependencies and conflicts have been declared." msgstr "" #: ../../ch-binary.rst:201 msgid "" "Instructions for configuring or using the package should not be included " "(that is what installation scripts, manual pages, info files, etc., are " "for). Copyright statements and other administrivia should not be included" " either (that is what the copyright file is for)." msgstr "" #: ../../ch-binary.rst:209 msgid "The single line synopsis" msgstr "" #: ../../ch-binary.rst:211 msgid "" "The single line synopsis should be kept brief---certainly under 80 " "characters." msgstr "" #: ../../ch-binary.rst:214 msgid "" "Do not include the package name in the synopsis line. The display " "software knows how to display this already, and you do not need to state " "it. Remember that in many situations the user may only see the synopsis " "line - make it as informative as you can." msgstr "" #: ../../ch-binary.rst:222 msgid "The extended description" msgstr "" #: ../../ch-binary.rst:224 msgid "" "Do not try to continue the single line synopsis into the extended " "description. This will not work correctly when the full description is " "displayed, and makes no sense where only the summary (the single line " "synopsis) is available." msgstr "" #: ../../ch-binary.rst:229 msgid "" "The extended description should describe what the package does and how it" " relates to the rest of the system (in terms of, for example, which " "subsystem it is which part of)." msgstr "" #: ../../ch-binary.rst:233 msgid "" "The description field needs to make sense to anyone, even people who have" " no idea about any of the things the package deals with. [#]_" msgstr "" #: ../../ch-binary.rst:239 msgid "Dependencies" msgstr "" #: ../../ch-binary.rst:241 msgid "" "Every package must specify the dependency information about other " "packages that are required for the first to work correctly." msgstr "" #: ../../ch-binary.rst:244 msgid "" "For example, a dependency entry must be provided for any shared libraries" " required by a dynamically-linked executable binary in a package." msgstr "" #: ../../ch-binary.rst:248 msgid "" "Packages are not required to declare any dependencies they have on other " "packages which are marked ``Essential`` (see below), and should not do so" " unless they depend on a particular version of that package. [#]_" msgstr "" #: ../../ch-binary.rst:252 msgid "" "Sometimes, unpacking one package requires that another package be first " "unpacked *and* configured. In this case, the depending package must " "specify this dependency in the ``Pre-Depends`` control field." msgstr "" #: ../../ch-binary.rst:256 msgid "" "You should not specify a ``Pre-Depends`` entry for a package before this " "has been discussed on the ``debian-devel`` mailing list and a consensus " "about doing that has been reached." msgstr "" #: ../../ch-binary.rst:260 msgid "" "The format of the package interrelationship control fields is described " "in :doc:`Declaring relationships between packages `." msgstr "" #: ../../ch-binary.rst:266 msgid "Virtual packages" msgstr "" #: ../../ch-binary.rst:268 msgid "" "Sometimes, there are several packages which offer more-or-less the same " "functionality. In this case, it's useful to define a *virtual package* " "whose name describes that common functionality. (The virtual packages " "only exist logically, not physically; that's why they are called " "*virtual*.) The packages with this particular function will then " "*provide* the virtual package. Thus, any other package requiring that " "function can simply depend on the virtual package without having to " "specify all possible packages individually." msgstr "" #: ../../ch-binary.rst:277 msgid "" "All packages should use virtual package names where appropriate, and " "arrange to create new ones if necessary. They should not use virtual " "package names (except privately, amongst a cooperating group of packages)" " unless they have been agreed upon and appear in the list of virtual " "package names. (See also :ref:`s-virtual`)" msgstr "" #: ../../ch-binary.rst:283 msgid "" "The latest version of the authoritative list of virtual package names can" " be found in the ``debian-policy`` package. It is also available from the" " Debian web mirrors at https://www.debian.org/doc/packaging-manuals" "/virtual-package-names-list.yaml." msgstr "" #: ../../ch-binary.rst:288 msgid "" "The procedure for updating the list is described in the preface to the " "list." msgstr "" #: ../../ch-binary.rst:294 msgid "Base system" msgstr "" #: ../../ch-binary.rst:296 msgid "" "The ``base system`` is a minimum subset of the Debian system that is " "installed before everything else on a new system. Only very few packages " "are allowed to form part of the base system, in order to keep the " "required disk usage very small." msgstr "" #: ../../ch-binary.rst:301 msgid "" "The base system consists of all those packages with priority ``required``" " or ``important``. Many of them will be tagged ``essential`` (see below)." msgstr "" #: ../../ch-binary.rst:308 msgid "Essential packages" msgstr "" #: ../../ch-binary.rst:310 msgid "" "Essential is defined as the minimal set of functionality that must be " "available and usable on the system at all times, even when packages are " "in the \"Unpacked\" state. Packages are tagged ``essential`` for a system" " using the ``Essential`` control field. The format of the ``Essential`` " "control field is described in :ref:`s-f-Essential`." msgstr "" #: ../../ch-binary.rst:316 msgid "" "Since these packages cannot be easily removed (one has to specify an " "extra *force option* to ``dpkg`` to do so), this flag must not be used " "unless absolutely necessary. A shared library package must not be tagged " "``essential``; dependencies will prevent its premature removal, and we " "need to be able to remove it when it has been superseded." msgstr "" #: ../../ch-binary.rst:322 msgid "" "Since dpkg will not prevent upgrading of other packages while an " "``essential`` package is in an unconfigured state, all ``essential`` " "packages must supply all of their core functionality even when " "unconfigured after being configured at least once. If the package cannot " "satisfy this requirement it must not be tagged as essential, and any " "packages depending on this package must instead have explicit dependency " "fields as appropriate." msgstr "" #: ../../ch-binary.rst:330 msgid "" "Maintainers should take great care in adding any programs, interfaces, or" " functionality to ``essential`` packages. Packages may assume that " "functionality provided by ``essential`` packages is always available " "without declaring explicit dependencies, which means that removing " "functionality from the Essential set is very difficult and is almost " "never done. Any capability added to an ``essential`` package therefore " "creates an obligation to support that capability as part of the Essential" " set in perpetuity." msgstr "" #: ../../ch-binary.rst:339 msgid "" "You must not tag any packages ``essential`` before this has been " "discussed on the ``debian-devel`` mailing list and a consensus about " "doing that has been reached." msgstr "" #: ../../ch-binary.rst:346 msgid "Maintainer Scripts" msgstr "" #: ../../ch-binary.rst:348 msgid "" "The package installation scripts should avoid producing output which is " "unnecessary for the user to see and should rely on ``dpkg`` to stave off " "boredom on the part of a user installing many packages. This means, " "amongst other things, not passing the ``--verbose`` option to ``update-" "alternatives``." msgstr "" #: ../../ch-binary.rst:354 msgid "" "Errors which occur during the execution of an installation script must be" " checked and the installation must not continue after an error." msgstr "" #: ../../ch-binary.rst:357 msgid "" "Note that in general :ref:`s-scripts` applies to package maintainer " "scripts, too." msgstr "" #: ../../ch-binary.rst:360 msgid "" "You should not use ``dpkg-divert`` on a file belonging to another package" " without consulting the maintainer of that package first. When adding or " "removing diversions, package maintainer scripts must provide the " "``--package`` flag to ``dpkg-divert`` and must not use ``--local``." msgstr "" #: ../../ch-binary.rst:365 msgid "" "All packages which supply an instance of a common command name (or, in " "general, filename) should generally use ``update-alternatives`` so that " "they can be installed together. If ``update-alternatives`` is not used, " "then each package must use ``Conflicts`` to ensure that other packages " "are removed. (In this case, it may be appropriate to specify a conflict " "against earlier versions of something that previously did not use " "``update-alternatives``; this is an exception to the usual rule that " "versioned conflicts should be avoided.)" msgstr "" #: ../../ch-binary.rst:374 msgid "" "Diversions are primarily intended as a tool for local administrators and " "local packages to override the behavior of Debian. While there are some " "circumstances where one Debian package may need to divert a file " "installed by another Debian package, such circumstances are rare. " "Maintainers should strongly prefer using other overriding mechanisms, " "instead of diversions, whenever those other mechanisms are sufficient to " "accomplish the same goal. In other words, diversions in packages should " "be considered a last resort. Diversion of a file in one Debian package by" " another Debian package should be coordinated between the maintainers of " "those packages." msgstr "" #: ../../ch-binary.rst:384 #, python-format msgid "" "One specific case of this rule is that configuration files used by " "``systemd`` components, such as `units, " "`_" " `udev rules, " "`_" " `tmpfiles.d, " "`_" " `modules-load.d, `_, `sysusers " "`_" " and other such files, including those specific to systemd daemons (e.g.:" " `/etc/systemd/system.conf). " "`_ must not be diverted by any Debian package. Instead, " "use `masking and drop-ins " "`_." msgstr "" #: ../../ch-binary.rst:401 msgid "" "Alternatives must not be used for ``systemd`` configuration files. The " "alternatives system does not know how to apply changes to services when " "updating alternatives, so the resulting behavior would be confusing and " "unpredictable. Instead, `aliases " "`_" " can be used to provide alternative implementations of the same named " "unit." msgstr "" #: ../../ch-binary.rst:411 msgid "Prompting in maintainer scripts" msgstr "" #: ../../ch-binary.rst:413 msgid "" "Package maintainer scripts may prompt the user if necessary. Prompting " "must be done by communicating through a program, such as ``debconf``, " "which conforms to the Debian Configuration Management Specification, " "version 2 or higher." msgstr "" #: ../../ch-binary.rst:418 msgid "" "Packages which are essential, or which are dependencies of essential " "packages, may fall back on another prompting method if no such interface " "is available when they are executed." msgstr "" #: ../../ch-binary.rst:422 msgid "" "The Debian Configuration Management Specification is included in the " "``debconf_specification`` files in the debian-policy package. It is also " "available from the Debian web mirrors at https://www.debian.org/doc" "/packaging-manuals/debconf_specification.html." msgstr "" #: ../../ch-binary.rst:427 msgid "" "Packages which use the Debian Configuration Management Specification may " "contain the additional package metadata files ``config`` and " "``templates``. ``config`` is an additional maintainer script used for " "package configuration, and ``templates`` contains templates used for user" " prompting. The ``config`` script might be run before the ``preinst`` " "script and before the package is unpacked or any of its dependencies or " "pre-dependencies are satisfied. Therefore it must work using only the " "tools present in *essential* packages. [#]_" msgstr "" #: ../../ch-binary.rst:436 msgid "" "Packages which use the Debian Configuration Management Specification must" " allow for translation of their user-visible messages by using a gettext-" "based system such as the one provided by the po-debconf package." msgstr "" #: ../../ch-binary.rst:440 msgid "" "Packages should try to minimize the amount of prompting they need to do, " "and they should ensure that the user will only ever be asked each " "question once. This means that packages should try to use appropriate " "shared configuration files (such as ``/etc/papersize`` and " "``/etc/news/server``), and shared debconf variables rather than each " "prompting for their own list of required pieces of information." msgstr "" #: ../../ch-binary.rst:447 msgid "" "It also means that an upgrade should not ask the same questions again, " "unless the user has used ``dpkg --purge`` to remove the package's " "configuration. The answers to configuration questions should be stored in" " an appropriate place in ``/etc`` so that the user can modify them, and " "how this has been done should be documented." msgstr "" #: ../../ch-binary.rst:453 msgid "" "If a package has a vitally important piece of information to pass to the " "user (such as \"don't run me as I am, you must edit the following " "configuration files first or you risk your system emitting badly-" "formatted messages\"), it should display this in the ``config`` or " "``postinst`` script and prompt the user to hit return to acknowledge the " "message. Copyright messages do not count as vitally important (they " "belong in ``/usr/share/doc/PACKAGE/copyright``); neither do instructions " "on how to use a program (these should be in on-line documentation, where " "all the users can see them)." msgstr "" #: ../../ch-binary.rst:463 msgid "" "Any necessary prompting should almost always be confined to the " "``config`` or ``postinst`` script. If it is done in the ``postinst``, it " "should be protected with a conditional so that unnecessary prompting " "doesn't happen if a package's installation fails and the ``postinst`` is " "called with ``abort-upgrade``, ``abort-remove`` or ``abort-deconfigure``." msgstr "" #: ../../ch-binary.rst:471 msgid "" "A sample implementation of such a whitelist written for the Mailman " "mailing list management software is used for mailing lists hosted by " "https://alioth-lists.debian.net/." msgstr "" #: ../../ch-binary.rst:476 msgid "" "The detailed procedure for gracefully orphaning a package can be found in" " the Debian Developer's Reference (see :ref:`s-related`)." msgstr "" #: ../../ch-binary.rst:481 msgid "" "The blurb that comes with a program in its announcements and/or " "``README`` files is rarely suitable for use in a description. It is " "usually aimed at people who are already in the community where the " "package is used." msgstr "" #: ../../ch-binary.rst:487 msgid "" "Essential is needed in part to avoid unresolvable dependency loops on " "upgrade. If packages add unnecessary dependencies on packages in this " "set, the chances that there **will** be an unresolvable dependency loop " "caused by forcing these Essential packages to be configured first before " "they need to be is greatly increased. It also increases the chances that " "frontends will be unable to **calculate** an upgrade path, even if one " "exists." msgstr "" #: ../../ch-binary.rst:495 msgid "" "Also, functionality is rarely ever removed from the Essential set, but " "*packages* have been removed from the Essential set when the " "functionality moved to a different package. So depending on these " "packages *just in case* they stop being essential does way more harm than" " good." msgstr "" #: ../../ch-binary.rst:502 msgid "" "Debconf or another tool that implements the Debian Configuration " "Management Specification will also be installed, and any versioned " "dependencies on it will be satisfied before preconfiguration begins." msgstr "" #~ msgid "" #~ "Native Debian packages (i.e., packages " #~ "which have been written especially for" #~ " Debian) whose version numbers include " #~ "dates should also follow these rules." #~ " If punctuation is desired between " #~ "the date components, remember that " #~ "hyphen (``-``) cannot be used in " #~ "native package versions. Period (``.``) " #~ "is normally a good choice." #~ msgstr "" #~ msgid "" #~ "If a package has a vitally " #~ "important piece of information to pass" #~ " to the user (such as \"don't " #~ "run me as I am, you must " #~ "edit the following configuration files " #~ "first or you risk your system " #~ "emitting badly-formatted messages\"), it " #~ "should display this in the ``config``" #~ " or ``postinst`` script and prompt " #~ "the user to hit return to " #~ "acknowledge the message. Copyright messages" #~ " do not count as vitally important" #~ " (they belong in " #~ "``/usr/share/doc/package/copyright``); neither do " #~ "instructions on how to use a " #~ "program (these should be in on-" #~ "line documentation, where all the users" #~ " can see them)." #~ msgstr "" #~ msgid "" #~ "All packages which supply an instance" #~ " of a common command name (or, " #~ "in general, filename) should generally " #~ "use ``update-alternatives``, so that " #~ "they may be installed together. If " #~ "``update-alternatives`` is not used, " #~ "then each package must use ``Conflicts``" #~ " to ensure that other packages are" #~ " removed. (In this case, it may " #~ "be appropriate to specify a conflict " #~ "against earlier versions of something " #~ "that previously did not use ``update-" #~ "alternatives``; this is an exception to" #~ " the usual rule that versioned " #~ "conflicts should be avoided.)" #~ msgstr "" #~ msgid "" #~ "Since dpkg will not prevent upgrading" #~ " of other packages while an " #~ "``essential`` package is in an " #~ "unconfigured state, all ``essential`` packages" #~ " must supply all of their core " #~ "functionality even when unconfigured. If " #~ "the package cannot satisfy this " #~ "requirement it must not be tagged " #~ "as essential, and any packages depending" #~ " on this package must instead have" #~ " explicit dependency fields as appropriate." #~ msgstr "" #~ msgid "" #~ "A ``.deb`` package contains two sets " #~ "of files: a set of files to " #~ "install on the system when the " #~ "package is installed, and a set of" #~ " files that provide additional metadata " #~ "about the package or which are " #~ "executed when the package is installed" #~ " or removed. This second set of " #~ "files is called *control information " #~ "files*. Among those files are the " #~ "package maintainer scripts and ``control``," #~ " the :ref:`binary package control file " #~ "` that contains the " #~ "control fields for the package. Other" #~ " control information files include " #~ ":ref:`symbols ` or " #~ ":ref:`shlibs ` used to" #~ " store shared library dependency " #~ "information and the ``conffiles`` file " #~ "that lists the package's configuration " #~ "files (described in :ref:`s-config-files`)." #~ msgstr "" #~ msgid "" #~ "There is unfortunately a collision of" #~ " terminology here between control " #~ "information files and files in the " #~ "Debian control file format. Throughout " #~ "this document, a *control file* refers" #~ " to a file in the Debian " #~ "control file format. These files are " #~ "documented in :doc:`Control files and " #~ "their fields `. Only " #~ "files referred to specifically as " #~ "*control information files* are the " #~ "files included in the control " #~ "information file member of the ``.deb``" #~ " file format used by binary packages." #~ " Most control information files are " #~ "not in the Debian control file " #~ "format." #~ msgstr "" #~ msgid "" #~ "Packages which use the Debian " #~ "Configuration Management Specification may " #~ "contain the additional control information " #~ "files ``config`` and ``templates``. ``config``" #~ " is an additional maintainer script " #~ "used for package configuration, and " #~ "``templates`` contains templates used for " #~ "user prompting. The ``config`` script " #~ "might be run before the ``preinst`` " #~ "script and before the package is " #~ "unpacked or any of its dependencies " #~ "or pre-dependencies are satisfied. " #~ "Therefore it must work using only " #~ "the tools present in *essential* " #~ "packages. [#]_" #~ msgstr ""