#
msgid ""
msgstr ""
-"Project-Id-Version: developers-reference 3.4.4\n"
-"POT-Creation-Date: 2010-06-20 09:22-0400\n"
-"PO-Revision-Date: 2011-02-28 02:27+0900\n"
-"Last-Translator: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>\n"
+"Project-Id-Version: developers-reference 3.4.5\n"
+"POT-Creation-Date: 2011-09-10 16:28-0400\n"
+"PO-Revision-Date: 2011-07-03 19:27+0900\n"
+"Last-Translator: Hideki Yamane <henrich@debian.org>\n"
"Language-Team: Debian JP Project <debian-doc@debian.or.jp>\n"
"Language: Japanese\n"
"MIME-Version: 1.0\n"
"tools, tools which help you, the Debian maintainer, create and maintain "
"excellent packages."
msgstr ""
-"Debian の品質は、<ulink url=\"&url-debian-policy;\">Debian Policy</ulink> に大"
-"きく依存しています。これは、全ての Debian パッケージが満たす必要がある基本的要求"
-"を明示的に規定している"
+"Debian の品質は、<ulink url=\"&url-debian-policy;\">Debian Policy</ulink> に"
+"大きく依存しています。これは、全ての Debian パッケージが満たす必要がある基本"
+"的要求を明示的に規定している"
+"多くの非常に優秀な人々が素晴らしいツールを作っており、このツールがあなた、つまり Debian のメンテナが素晴らしいパッケージを作り、維持していくのを手助けしてくれます。"
# type: Content of: <chapter><para>
#. type: Content of: <chapter><para>
#: best-pkging-practices.dbk:18
+#, fuzzy
msgid ""
"This chapter provides some best practices for Debian developers. All "
"recommendations are merely that, and are not requirements or policy. These "
"are just some subjective hints, advice and pointers collected from Debian "
"developers. Feel free to pick and choose whatever works best for you."
msgstr ""
+"この章では、Debian 開発者へのベストプラクティスをいくつか提供します。すべての"
+"勧めは単なる勧めであり、要求事項やポリシーではありません。"
+"あなたにとって一番うまくいくのを、ご自由にどうぞ選んでください。"
# type: Content of: <chapter><section><title>
#. type: Content of: <chapter><section><title>
# type: Content of: <chapter><section><para>
#. type: Content of: <chapter><section><para>
#: best-pkging-practices.dbk:26
+#, fuzzy
msgid ""
"The following recommendations apply to the <filename>debian/rules</filename> "
"file. Since <filename>debian/rules</filename> controls the build process "
"and selects the files which go into the package (directly or indirectly), "
"it's usually the file maintainers spend the most time on."
msgstr ""
+"以下の推奨事項は、<filename>debian/rules</filename> ファイルに適用されます。"
+"<filename>debian/rules</filename> "
# type: Content of: <chapter><section><section><title>
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:32
msgid "Helper scripts"
-msgstr "補助スクリプト"
+msgstr "ヘルパースクリプト"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
"with bugs? Also, supposing the menu directory changed, every package would "
"have to be changed."
msgstr ""
+"<filename>debian/rules</filename> でヘルパースクリプトを使う根拠は、多くの"
+"パッケージ間でメンテナらに共通のロジックを利用・共有させるようになるからです。"
+"メニューエントリのインストールについての問いを例にとってみましょう: ファイルを <filename>"
+"/usr/share/menu</filename> (必要であれば、実行形式のバイナリのメニューファイル"
+"の場合 <filename>/usr/lib/menu</filename>) に置き、メンテナスクリプトにメニュー"
+"エントリを登録・解除するためのコマンドを追加する必要があります。これはパッケージ"
+"が行う、非常に一般的なことです。なぜ個々のメンテナがこれらのすべてを自分で書き直し、"
+"時にはバグを埋め込む必要があるでしょう? また、メニューディレクトリが変更された場合、"
+"すべてのパッケージを変更する必要があります。"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
"just need to be rebuilt with the new version of the helper and no other "
"changes."
msgstr ""
+"ヘルパースクリプトがこれらの問題を引き受けてくれます。ヘルパースクリプトの"
+"期待するやり方に従っているならば、ヘルパースクリプトはすべての詳細について"
+"考慮をします。ポリシーの変更はヘルパースクリプト中で行えます; そして、"
+"パッケージを新しいバージョンのヘルパースクリプトでリビルドする必要がある"
+"だけです。他に何の変更も必要ありません。"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
"helper scripts, where useful, in conjunction with hand-crafted commands in "
"<filename>debian/rules</filename>."
msgstr ""
+"<xref linkend=\"tools\"/> には、複数の異なったヘルパーが含まれています。"
+"もっとも一般的で (我々の意見では) ベストなヘルパーシステムは <systemitem "
+"role=\"package\">debhelper</systemitem> です。<systemitem role=\"package\">"
+"debmake</systemitem> のような、以前のヘルパーシステムはモノリシックでした: "
+"使えそうなヘルパーの一部を取り出して選ぶことはできず、何を行うにもヘルパー"
+"を使う必要がありました。ですが、<systemitem role=\"package\">debhelper"
+"</systemitem> は、いくつもの分割された小さな <command>dh_*</command> "
+"プログラムです。たとえば、<command>dh_installman</command> は man ページを"
+"インストールして圧縮し、<command>dh_installmenu</command> は menu ファイル"
+"をインストールするなどします。つまり、<filename>debian/rules</filename> "
+"内で使える部分では小さなヘルパースクリプトを使い、手製のコマンドを使うと"
+"いった十分な柔軟性を与えてくれます。"
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:66
+#, fuzzy
msgid ""
"You can get started with <systemitem role=\"package\">debhelper</systemitem> "
"by reading <citerefentry> <refentrytitle>debhelper</refentrytitle> "
"helper, you do need to take the time to learn to use that helper, to learn "
"its expectations and behavior."
msgstr ""
+"<citerefentry> <refentrytitle>debhelper</refentrytitle> <manvolnum>1</manvolnum> "
+"</citerefentry> を読んで、パッケージに付属している例を参照すれば、<systemitem "
+"role=\"package\">debhelper</systemitem> を使い始められます。 <systemitem "
+"role=\"package\">dh-make</systemitem> パッケージ (<xref linkend=\"dh-make\"/> "
+"参照) の <command>dh_make</command> は、素のソースパッケージを <systemitem role="
+"\"package\">debhelper</systemitem>化されたパッケージに変換するのに利用できます。"
+"ですが、この近道では個々の <command>dh_*</command> ヘルパーをわざわざ理解する"
+"必要がないので納得することができないでしょう。ヘルパースクリプトを使おうとする"
+"のであれば、そのヘルパーを使うこと、つまり前提と動作を学ぶのに時間を割く必要が"
+"あります。"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
"examples of vanilla <filename>debian/rules</filename> files are available at "
"<ulink url=\"&url-rules-files;\"></ulink>."
msgstr ""
+"いかなるヘルパーシステムの複雑さも学ぶ必要がないので、素の <filename>debian"
+"/rules</filename> ファイルのほうが良いと考える人もいます。この判断は完全に"
+"あなた次第です。あなたに合っているのを選んでください。素の <filename>debian"
+"/rules</filename> ファイルの多くの例は <ulink url=\"&url-rules-files;\">"
+"</ulink> で入手できます。"
# type: Content of: <chapter><section><section><title>
#. type: Content of: <chapter><section><section><title>
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:90
+#, fuzzy
msgid ""
"Big, complex packages may have many bugs that you need to deal with. If you "
"correct a number of bugs directly in the source, and you're not careful, it "
"the total set of diffs (e.g., from <filename>.diff.gz</filename>) and work "
"out which patch sets to back out as a unit as bugs are fixed upstream."
msgstr ""
+"巨大で、複雑なパッケージには対処が必要なたくさんのバグが含まれているかも"
+"しれません。直接ソース中で大量のバグを修正し、あまり注意を払っていなかった"
+"場合、適用した様々なパッチを識別するのは難しいことになるでしょう。"
+"(全てではなく) 幾つか修正を取り入れた新しい開発元のバージョンへパッケージを"
+"更新する必要が出た場合、とても悲惨なことになります。"
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:99
"<filename>debian/patches/series</filename> are automatically applied. As "
"the name implies, patches can be managed with <command>quilt</command>."
msgstr ""
+"幸いなことに、ソースフォーマット“3.0 (quilt)”では、パッチシステムを設定するために "
+"<filename>debian/rules</filename> を変更することなく、パッチを分割して保持できる"
+"ようになっています。パッチは <filename>debian/patches/</filename> に保持され、"
+"ソースパッケージが展開されるときに <filename>debian/patches/series</filename> "
+"に記載されているパッチが自動的に適用されます。名前が指すように、パッチは "
+"<command>quilt</command> で管理することができます。"
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:107
"reverted in the <literal>clean</literal> rule, through a dependency on the "
"<literal>unpatch</literal> rule."
msgstr ""
+"より古いソースフォーマット“1.0”を使っている場合でも、パッチを分割することは"
+"可能ですが、専用のパッチシステムを使う必要があります: パッチファイルは Debian "
+"パッチファイル (<filename>.diff.gz</filename>) 内に組み込まれ、通常 <filename>"
+"debian/</filename> ディレクトリ内にあります。違いは、すぐに <command>dpkg-source"
+"</command> では適用されないが、<filename>debian/rules</filename> の <literal>"
+"build</literal> ルールで <literal>patch</literal> ルールへの依存を通じて適用"
+"されることだけです。逆に言うと、これらのパッチは <literal>unpatch</literal> "
+"ルールへの依存を通じて <literal>clean</literal> ルールで外されます。"
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:119
"the above, and also allows to manage patch series. See the <systemitem role="
"\"package\">quilt</systemitem> package for more information."
msgstr ""
+"<command>quilt</command> はこの作業にお勧めのツールです。上記の全てを行う上、"
+"パッチ一覧の管理も可能です。詳細な情報は <systemitem role=\"package\">quilt"
+"</systemitem> パッケージを参照してください。"
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:125
"the patch system integrated with <systemitem role=\"package\">cdbs</"
"systemitem>."
msgstr ""
+"他にもパッチを管理するツールはあります。<command>dpatch</command> や、パッチ"
+"システムが統合されている <systemitem role=\"package\">cdbs</systemitem> などです。"
# type: Content of: <chapter><section><section><title>
#. type: Content of: <chapter><section><section><title>
# type: Content of: <chapter><section><section><section><screen>
#. type: Content of: <chapter><section><section><section><screen>
#: best-pkging-practices.dbk:412
-#, fuzzy, no-wrap
+#, no-wrap
msgid ""
" Source: vim\n"
" Section: editors\n"
" Vcs-Browser: http://svn.debian.org/wsvn/pkg-vim/trunk/packages/vim\n"
" Homepage: http://www.vim.org\n"
msgstr ""
-"\n"
" Source: vim\n"
" Section: editors\n"
" Priority: optional\n"
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:507
msgid "Common errors in changelog entries"
-msgstr ""
+msgstr "changelog のエントリ中のよくある間違い"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
"The following examples demonstrate some common errors or examples of bad "
"style in changelog entries."
msgstr ""
+"以下の例で、changelog エントリ中のよくある間違いや間違ったスタイルの例を"
+"挙げます。"
# type: Content of: <chapter><section><section><screen>
#. type: Content of: <chapter><section><section><screen>
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:516
msgid "This doesn't tell readers anything too useful, obviously."
-msgstr ""
+msgstr "これは、全く読み手に何も有用なことを教えてくれません。"
# type: Content of: <chapter><section><section><screen>
#. type: Content of: <chapter><section><section><screen>
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:522
msgid "What was the patch about?"
-msgstr ""
+msgstr "何についてのパッチですか?"
# type: Content of: <chapter><section><section><screen>
#. type: Content of: <chapter><section><section><screen>
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:535
+#, fuzzy
msgid ""
"Too many acronyms, and it's not overly clear what the, uh, fsckup (oops, a "
"curse word!) was actually about, or how it was fixed."
msgstr ""
+"略称が多すぎ、どうやって修正したのか"
# type: Content of: <chapter><section><section><screen>
#. type: Content of: <chapter><section><section><screen>
"Where's the description? If you can't think of a descriptive message, start "
"by inserting the title of each different bug."
msgstr ""
+"説明はどこ? 説明文を考えられないのなら、それぞれのバグのタイトルを入れるところ"
+"から始めてください。"
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:566
+#, fuzzy
msgid "Supplementing changelogs with <filename>NEWS.Debian</filename> files"
-msgstr ""
+msgstr "<filename>NEWS.Debian</filename> ファイルで changelog を"
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:568
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:1314
msgid "Example, taken from the geneweb package templates:"
-msgstr ""
+msgstr "geneweb パッケージのテンプレートを例にとってみましょう:"
#. type: Content of: <chapter><section><section><section><screen>
#: best-pkging-practices.dbk:1317
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:1455
msgid "Packages using <command>autoconf</command>/<command>automake</command>"
-msgstr "<command>autoconf</command>/<command>automake</command> を使っているパッケージ"
+msgstr ""
+"<command>autoconf</command>/<command>automake</command> を使っているパッケー"
+"ジ"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
"search .|grep transitional</command>."
msgstr ""
+#. type: Content of: <chapter><section><section><para>
+#: best-pkging-practices.dbk:1674
+msgid ""
+"Also, it is recommended to adjust its section to <literal>oldlibs</literal> "
+"and its priority to <literal>extra</literal> in order to ease "
+"<command>deborphan</command>'s job."
+msgstr ""
+
# type: Content of: <chapter><section><title>
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1676
+#: best-pkging-practices.dbk:1683
msgid "Best practices for <filename>.orig.tar.{gz,bz2,lzma}</filename> files"
msgstr ""
"<filename>.orig.tar.{gz,bz2,lzma}</filename> についてのベストプラクティス"
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1678
+#: best-pkging-practices.dbk:1685
msgid ""
"There are two kinds of original source tarballs: Pristine source and "
"repackaged upstream source."
# type: Content of: <chapter><section><section><section><title>
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1682
+#: best-pkging-practices.dbk:1689
msgid "Pristine source"
msgstr ""
#. type: Content of: <chapter><section><section><section><para><footnote><para>
-#: best-pkging-practices.dbk:1686
+#: best-pkging-practices.dbk:1693
msgid ""
"We cannot prevent upstream authors from changing the tarball they distribute "
"without also incrementing the version number, so there can be no guarantee "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1684
+#: best-pkging-practices.dbk:1691
msgid ""
"The defining characteristic of a pristine source tarball is that the "
"<filename>.orig.tar.{gz,bz2,lzma}</filename> file is byte-for-byte identical "
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1704
+#: best-pkging-practices.dbk:1711
msgid ""
"There is no universally accepted guidelines that upstream authors follow "
"regarding to the directory structure inside their tarball, but <command>dpkg-"
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1712
+#: best-pkging-practices.dbk:1719
msgid "It unpacks the tarball in an empty temporary directory by doing"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><screen>
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><screen>
-#: best-pkging-practices.dbk:1715
+#: best-pkging-practices.dbk:1722
#, no-wrap
msgid "zcat path/to/<replaceable>packagename</replaceable>_<replaceable>upstream-version</replaceable>.orig.tar.gz | tar xf -\n"
msgstr "zcat path/to/<replaceable>パッケージ名</replaceable>_<replaceable>upstream-version</replaceable>.orig.tar.gz | tar xf -\n"
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1720
+#: best-pkging-practices.dbk:1727
msgid ""
"If, after this, the temporary directory contains nothing but one directory "
"and no other files, <command>dpkg-source</command> renames that directory to "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1729
+#: best-pkging-practices.dbk:1736
msgid ""
"Otherwise, the upstream tarball must have been packaged without a common top-"
"level directory (shame on the upstream author!). In this case, "
# type: Content of: <chapter><section><section><section><title>
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1740
+#: best-pkging-practices.dbk:1747
msgid "Repackaged upstream source"
msgstr "upstream のソースをパッケージしなおす"
# type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1742
+#: best-pkging-practices.dbk:1749
msgid ""
"You <emphasis role=\"strong\">should</emphasis> upload packages with a "
"pristine source tarball if possible, but there are various reasons why it "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1749
+#: best-pkging-practices.dbk:1756
msgid ""
"In these cases the developer must construct a suitable <filename>.orig.tar."
"{gz,bz2,lzma}</filename> file himself. We refer to such a tarball as a "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1758
+#: best-pkging-practices.dbk:1765
msgid ""
"There may be cases where it is desirable to repackage the source even though "
"upstream distributes a <filename>.tar.{gz,bz2,lzma}</filename> that could in "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1767
+#: best-pkging-practices.dbk:1774
msgid "A repackaged <filename>.orig.tar.{gz,bz2,lzma}</filename>"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1772
+#: best-pkging-practices.dbk:1779
msgid ""
"<emphasis role=\"strong\">should</emphasis> be documented in the resulting "
"source package. Detailed information on how the repackaged source was "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote><para>
-#: best-pkging-practices.dbk:1787
+#: best-pkging-practices.dbk:1794
msgid ""
"As a special exception, if the omission of non-free files would lead to the "
"source failing to build without assistance from the Debian diff, it might be "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1785
+#: best-pkging-practices.dbk:1792
msgid ""
"<emphasis role=\"strong\">should not</emphasis> contain any file that does "
"not come from the upstream author(s), or whose contents has been changed by "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1798
+#: best-pkging-practices.dbk:1805
msgid ""
"<emphasis role=\"strong\">should</emphasis>, except where impossible for "
"legal reasons, preserve the entire building and portablility infrastructure "
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1807
+#: best-pkging-practices.dbk:1814
msgid ""
"(<emphasis>Rationale:</emphasis> It is common for Debian users who need to "
"build software for non-Debian platforms to fetch the source from a Debian "
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1814
+#: best-pkging-practices.dbk:1821
msgid ""
"<emphasis role=\"strong\">should</emphasis> use "
"<filename><replaceable>packagename</replaceable>-<replaceable>upstream-"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1822
+#: best-pkging-practices.dbk:1829
msgid ""
"<emphasis role=\"strong\">should</emphasis> be gzipped or bzipped with "
"maximal compression."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1829
+#: best-pkging-practices.dbk:1836
msgid "Changing binary files"
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1831
+#: best-pkging-practices.dbk:1838
msgid ""
"Sometimes it is necessary to change binary files contained in the original "
"tarball, or to add binary files that are not in it. This is fully supported "
# type: Content of: <chapter><section><section><title>
#. type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1846
+#: best-pkging-practices.dbk:1853
msgid "Best practices for debug packages"
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1848
+#: best-pkging-practices.dbk:1855
msgid ""
"A debug package is a package with a name ending in -dbg, that contains "
"additional information that <command>gdb</command> can use. Since Debian "
# type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1856
+#: best-pkging-practices.dbk:1863
msgid ""
"It is up to a package's maintainer whether to create a debug package or "
"not. Maintainers are encouraged to create debug packages for library "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1866
+#: best-pkging-practices.dbk:1873
msgid ""
"Some debug packages may contain an entire special debugging build of a "
"library or other binary, but most of them can save space and build time by "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1878
+#: best-pkging-practices.dbk:1885
msgid ""
"The debugging symbols can be extracted from an object file using "
"<command>objcopy --only-keep-debug</command>. Then the object file can be "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1886
+#: best-pkging-practices.dbk:1893
msgid ""
"The <command>dh_strip</command> command in <systemitem role=\"package"
"\">debhelper</systemitem> supports creating debug packages, and can take "
msgstr ""
#. type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1893
+#: best-pkging-practices.dbk:1900
msgid ""
"Note that the debug package should depend on the package that it provides "
"debugging symbols for, and this dependency should be versioned. For example:"
# type: Content of: <chapter><section><section><screen>
#. type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:1897
+#: best-pkging-practices.dbk:1904
#, no-wrap
msgid "Depends: libfoo (= ${binary:Version})\n"
msgstr "Depends: libfoo (= ${binary:Version})\n"
+
+# type: Content of: <chapter><section><title>
+#. type: Content of: <chapter><section><section><title>
+#: best-pkging-practices.dbk:1908
+#, fuzzy
+#| msgid "Best practices for maintainer scripts"
+msgid "Best practices for meta-packages"
+msgstr "メンテナスクリプトのベストプラクティス"
+
+#. type: Content of: <chapter><section><section><para>
+#: best-pkging-practices.dbk:1910
+msgid ""
+"A meta-package is a mostly empty package that makes it easy to install a "
+"coherent set of packages that can evolve over time. It achieves this by "
+"depending on all the packages of the set. Thanks to the power of APT, the "
+"meta-package maintainer can adjust the dependencies and the user's system "
+"will automatically get the supplementary packages. The dropped packages that "
+"were automatically installed will be also be marked as removal candidates "
+"(and are even automatically removed by <command>aptitude</command>). "
+"<systemitem role=\"package\">gnome</systemitem> and <systemitem role="
+"\"package\">linux-image-amd64</systemitem> are two examples of meta-packages "
+"(built by the source packages <systemitem role=\"package\">meta-gnome2</"
+"systemitem> and <systemitem role=\"package\">linux-latest</systemitem>)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><para>
+#: best-pkging-practices.dbk:1924
+msgid ""
+"The long description of the meta-package must clearly document its purpose "
+"so that the user knows what he will lose if he removes the package. Being "
+"explicit about the consequences is recommended. This is particularly "
+"important for meta-packages which are installed during initial installation "
+"and that have not been explicitly installed by the user. Those tend to be "
+"important to ensure smooth system upgrades and the user should be "
+"discouraged from uninstalling them to avoid potential breakages."
+msgstr ""