# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018, 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 <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Debian Policy Manual 4.1.6.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-10 16:09+0000\n"
"PO-Revision-Date: 2018-07-28 12:45+0800\n"
"Last-Translator: Hideki Yamane <henrich@debian.org>\n"
"Language-Team: Japanese <debian-doc@debian.or.jp>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.4.0\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 ""
"Debian ディストリビューションは ``dpkg`` と呼ばれる Debian パッケージ管理システムに"
"基礎を置いています。このため、Debian ディストリビューションに含まれる全てのパッケージは ``.deb`` ファイル形式で提供されなければなりません。"

#: ../../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 "
"*control information files*. Among those files are the package maintainer"
" scripts and ``control``, the :ref:`binary package control file "
"<s-binarycontrolfiles>` that contains the control fields for the package."
" Other control information files include :ref:`symbols <s-sharedlibs-"
"symbols>` or :ref:`shlibs <s-sharedlibs-shlibdeps>` 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 ""
"``.deb`` パッケージは二つのファイルの集合が含まれます。"
"パッケージインストールの際にシステムにインストールされる一連のファイル群と、"
"パッケージに対する追加のメタデータの提供や、パッケージインストールや削除の際に実行するための一連のファイル群です。"
"二番目のファイル群を *制御情報ファイル* と呼びます。"
"これらのファイルには、パッケージメンテナスクリプトや ``control`` ファイル、"
"パッケージのコントロールフィールドを収録した :ref:`バイナリパッケージコントロールファイル <s-binarycontrolfiles>` などがあります。"
"その他の制御情報ファイルには、共有ライブラリの依存情報を格納するのに用いる :ref:`symbols <s-sharedlibs-symbols>` と :ref:`shlibs <s-sharedlibs-shlibdeps>` "
"や、パッケージ設定ファイルを列挙した ``conffiles`` (:ref:`s-config-files` で詳説) などがあります。"

#: ../../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 <ch-controlfields>`. 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 ""
"制御情報ファイル群と、Debian コントロールファイルフォーマット間に残念ながら用語の衝突があります。"
"この文書では、*コントロールファイル (control file)* は Debian コントロールファイルフォーマットにそったファイルを指します。"
"それらファイルについては :doc:`Control files and their fields <ch-controlfields>` "
"で文書化されています。*制御情報ファイル* として参照されるファイルとは、バイナリパッケージで利用される "
"``.deb`` ファイルフォーマットの制御情報ファイルのメンバとして含まれているもののみです。"
"殆どの制御情報ファイルは、Debian 制御情報ファイル形式ではありません。"

#: ../../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 """
"全てのパッケージは Debian アーカイブ内において重複しない名前を持っていなければなりません。"

#: ../../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 ""
"パッケージ名はコントロールフィールド ``Package`` に含まれます。また、その"
"フォーマットは :ref:`s-f-Package` で記載されています。パッケージ名は "
"``.deb`` ファイルのファイル名の一部としても含まれています。"

#: ../../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 ""
"各パッケージはコントロールフィールド ``Version`` にバージョン番号を持ちます。"
"また、そのフォーマットは :ref:`s-f-Version` で記載されています。"

#: ../../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 ""
"もし上流のパッケージが問題のあるバージョン番号形式になっているならば、"
"``Version`` フィールドではまともな形式に変換すべきです。"

#: ../../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 ""
"一般的に、Debian パッケージは上流ソースと同じバージョン番号を使うべきです。"
"しかし、上流のバージョン番号が日付に基づくような場合 (例えば、開発中や \"snapshot\" "
"リリースの場合) には、パッケージ管理システムはこのようなバージョン番号を"
"正しく順序判断することができません。例えば、dpkg は \"96May01\" を" "
"\"96Dec24\" よりも大きいと判断するでしょう。"

#: ../../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 ""
"そのような場合に、今後の新しい上流バージョンに対して epoch を使わなくて"
"済むようにするためには、上流のバージョン番号を順序づけが正しく行われるような"
"方法に変更すべきです。具体的には、日付を元にしたバージョン番号部を 4 桁の年、"
"2 桁の月、2 桁の日で、各部の間に区切り文字を挿入可、と言うように直すべきです。"

#: ../../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 package versions. Period "
"(``.``) is normally a good choice."
msgstr ""
"Debian 固有のパッケージ (つまり、Debian 向けに特別に書かれたパッケージ) "
"の日付を含んだバージョン番号は、同じ規則に従うべきです。"
"日付の各部の間に区切り文字を含めたい場合、ハイフン (``-``) "
"は固有パッケージのバージョンには使えないことに注意してください。"
"通常は、ピリオド (``.``) が適切です。"

#: ../../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 ""
"全てのパッケージには、以下で記載する ``orphaned`` パッケージを除いて、"
"一人または一グループの Debian メンテナを持たなければなりません。メンテナは、"
"個人であっても、メーリングリストなどの共通の一つのメールアドレスで連絡の"
"取れるグループであってもかまいません。メンテナは、Debian パッケージファイルの保守、"
"すなわち報告されたバグに対して適切に判断・応答すること、新しいバージョンのアップロード "
"(直接あるいはスポンサー経由で) を行うこと、そのパッケージが適切なアーカイブエリアに"
"置かれていること、パッケージの安定度や有用性にしたがって適切なディストリビューションに"
"収録されていること、有用性が失われたか保守不能になった場合パッケージを Debian "
"ディストリビューションから削除する要求を出すことについて、責任を持ちます。"

#: ../../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 ""
"Debian パッケージのメンテナは各パッケージの ``Maintainer`` 制御フィールドに、"
"正しい名前と有効な電子メールアドレスの両方により指定されていなければなりません。"
"``Maintainer`` 制御フィールド内の電子メールアドレスは、Debian でパッケージに関して"
"自動的にメールを送るのに使われる役割のアカウントからのメールを受け取らなければいけません。"
"これは、バグトラッキングシステムからの SPAM でないメール、Debian アーカイブ管理"
"ソフトウェアからのすべてのメール、およびそれ以外にもプロジェクトで合意されている"
"決まった役割のアカウントと自動送信プロセスからのメールは、受け取らなければならないということです。 [#]_ "
"もしその人がいくつかのパッケージを管理している場合、個々のパッケージの ``Maintainer`` "
"フィールドに同じ形式の名前と電子メールアドレスを記入すべきです。"

#: ../../ch-binary.rst:163
msgid ""
"The format of the ``Maintainer`` control field is described in "
":ref:`s-f-Maintainer`."
msgstr ""
"``Maintainer`` フィールドの書式は、:ref:`s-f-Maintainer` で記載されています。"

#: ../../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 ""
"パッケージのメンテナがメールアドレスを共有するチームである場合、``Uploaders`` 制御"
"フィールドが必ず存在し、個人の電子メールアドレスを付けてひとりの人物が指定されて"
"いなければいけません。このフィールドの書式は、:ref:`s-f-Uploaders` を参照ください。"

#: ../../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 "
"<packages@qa.debian.org>``. These packages are considered maintained by "
"the Debian project as a whole until someone else volunteers to take over "
"maintenance.  [#]_"
msgstr ""
"orphaned パッケージとは、現在メンテナのいないパッケージのことです。orphaned "
"パッケージでは、``Maintainer`` 制御フィールドに ``Debian QA Group <packages@qa.debian.org>`` "
"を設定しなければいけません。このようなパッケージは、保守の志願者が現れない限り Debian "
"プロジェクト全体で保守されているとみなされます。 [#]_"

#: ../../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 ""
"全ての Debian パッケージは、パッケージの簡潔な説明文と、やや詳細な説明文を含む ``Description`` フィールドを持たなければなりません。"
"``Description`` フィールドの書式の技術的詳細は :ref:`s-f-Description` に記載されています。"

#: ../../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 ""
"説明文にはパッケージ間の重要な依存関係 (dependency) や競合関係 (conflict) の"
"情報も示されているべきです。そうでないと、ユーザにはなぜ競合関係や依存関係の不具合が起きているのかが分かりません。"

#: ../../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 ""
"また、そのパッケージを設定したり使ったりするための解説を含めるべきではありません "
"(それはインストールスクリプト、マニュアルページ、Infoファイルなどで扱われるべきです)。"
"著作権表示やその他管理に関係する種々のことも含まれるべきではありません。"
"それら向けには copyright ファイルが用意されています。"

#: ../../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 ""
"一行による要約は簡潔にすべきです。半角換算で 80 文字以下としてください。"

#: ../../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 ""
"パッケージ名を要約 (Synopsis) の行に入れないでください。入れなくても、表示"
"ソフトウェアはパッケージ名を自動的に表示するようになっています。多くの場合、"
"ユーザの目にふれるのはこの要約行だけなので、なるべく分かりやすい要約にする"
"ようにしてください。"

#: ../../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 ""
"詳細の解説部分はそのパッケージ自体の説明 (例えば、このパッケージが Debian "
"システム全体の中の、どの部分集合に属しているのか) について記します。"

#: ../../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 ""
"但し、``Essential`` (下記参照) と指定されているパッケージに対して、それ以外のパッケージが依存関係を宣言する必要はありません。"
"また、そのようなパッケージの特定のバージョンに依存しているのでなければ、依存関係を宣言すべきではありません。 [#]_"

#: ../../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 ""
"時々、あるパッケージが、それを展開する前にもう一つのパッケージが展開され *かつ* 設定されていることを必要とすることがあります。"
"この場合、そのパッケージには ``Pre-Depends`` エントリを指定しなければなりません。"

#: ../../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 ""
"``debian-devel`` メーリングリストで議論して同意が得られる前に、パッケージに ``Pre-Depends`` エントリを指定するべきではありません。"

#: ../../ch-binary.rst:260
msgid ""
"The format of the package interrelationship control fields is described "
"in :doc:`Declaring relationships between packages <ch-relationships>`."
msgstr ""
"パッケージ相互関係を指定するコントロールフィールドの書式は :doc:`Declaring relationships between packages <ch-relationships>` に記載されています。"

#: ../../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 ""
"全てのパッケージはそうするのが適当なときには仮想パッケージ名を使うべきで、"
"もし必要ならば新しい仮想パッケージ名を作るようにしなければなりません。"
"但し、同意が得られ、仮想パッケージ名の一覧に掲載されるまで、新しい仮想パッケージ名"
"を使うべきではありません (非公式に、互いに関連する一群のパッケージの間で使う場合は除く)。"
"この項に関しては、:ref:`s-virtual` を参照下さい。"

#: ../../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 ""
"正式な仮想パッケージ名の一覧の最新版は ``debian-policy`` パッケージに同封"
"されています。また、Debian ウェブミラーサーバの "
"https://www.debian.org/doc/packaging-manuals/virtual-package-names-list.yaml にあります。"

#: ../../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 "Base システム"

#: ../../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 ""
"``base システム`` は、新しいシステムに於いて他の全てに先だってインストールされる、"
"Debian システムの最小のサブセットを形成します。従って、必要となるディスク使用量"
"を非常に小さく保つため、ごく少数のパッケージのみが base システムの一部となること"
"を認められています。"

#: ../../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 ""
"base システムはプライオリティ評価が ``required`` と ``important`` のパッケージ"
"全体で構成されています。また、それらの大半には ``essential`` 指定 (下記参照) "
"が付加されているでしょう。"

#: ../../ch-binary.rst:308
msgid "Essential packages"
msgstr "Essential パッケージ"

#: ../../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 ""
"Essential は、パッケージ群が展開状態 (Unpacked) でも、システム上で提供され"
"使用できなければならない最小の機能の集合として定義されています。そのような"
"パッケージには ``Essential`` コントロールフィールドで ``Essential`` 指定が"
"付加されています。``Essential`` コントロールフィールドの書式は :ref:`s-f-Essential` "
"に記載されています。"

#: ../../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 ""
"これらのパッケージは簡単には削除できません (削除するには ``dpkg`` に特別な "
"*強制 (force) オプション* を指定しなければなりません)。このため、このフラグは"
"どうしても必要な場合にのみ使うようにしなければなりません。共有ライブラリの"
"パッケージに *Essential* 指定をしてはいけません。依存関係により誤った削除を"
"阻止できますし、新しいものに入れ替える際には上書きできるようになっている必要"
"があるからです。"

#: ../../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. 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 ""
"dpkg は ``Essential`` パッケージが未設定な状態でも他のパッケージの"
"アップグレードを止めることはありませんので、``Essential`` パッケージは"
"すべて、未設定状態でも基本機能はすべて提供している必要があります。"
"あるパッケージがこの条件を満たせない場合には、そのパッケージに"
"``Essential`` 指定を行ってはいけませんし、そのパッケージに依存する他の"
"パッケージは明示的に適切な依存関係フィールドを与えなければいけません。"

#: ../../ch-binary.rst:329
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 ""
"メンテナは、プログラム、インターフェース、機能を ``essential`` パッケージに"
"加える際には細心の注意を払う必要があります。パッケージは ``essential`` "
"パッケージの提供する機能は明示的な依存関係の宣言なしに常に提供されていること"
"を期待してよく、逆に Essential パッケージ群から機能を削除することは非常に"
"難しく、ほとんどできないものになります。また、``essential`` パッケージに"
"機能を加えることは、その機能を Essential 群で永久にサポートする義務を負わせる"
"ことになります。"

#: ../../ch-binary.rst:338
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 ""
"``debian-devel`` メーリングリストで議論して同意が得られない限り、"
"パッケージに ``Essential`` 指定を付加してはなりません。"

#: ../../ch-binary.rst:345
msgid "Maintainer Scripts"
msgstr "メンテナスクリプト"

#: ../../ch-binary.rst:347
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 ""
"パッケージのインストールスクリプトでは、ユーザにとって見る必要がない情報を"
"出力することを避けるべきです。また、大量のパッケージをインストールする際に"
"ユーザが退屈するのを避けるのも、``dpkg`` に任せておくべきです。中でも、"
"``update-alternatives`` に ``--verbose`` オプションを渡さないようにしましょう。"

#: ../../ch-binary.rst:353
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:356
msgid ""
"Note that in general :ref:`s-scripts` applies to package maintainer "
"scripts, too."
msgstr ""

#: ../../ch-binary.rst:359
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:364
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 ""

#: ../../ch-binary.rst:376
msgid "Prompting in maintainer scripts"
msgstr ""

#: ../../ch-binary.rst:378
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:383
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:387
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:392
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 ""

#: ../../ch-binary.rst:401
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:405
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:412
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:418
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:428
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:436
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:441
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:446
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:452
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:460
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:467
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 ""

