msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2010-05-31 19:21-0400\n"
+"POT-Creation-Date: 2011-10-12 09:49+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
-"Content-Transfer-Encoding: ENCODING"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
#. type: Content of: <chapter><title>
#: best-pkging-practices.dbk:7
msgid ""
"Important news about changes in a package can also be put in "
"<filename>NEWS.Debian</filename> files. The news will be displayed by tools "
-"like apt-listchanges, before all the rest of the changelogs. This is the "
-"preferred means to let the user know about significant changes in a "
-"package. It is better than using debconf notes since it is less annoying "
-"and the user can go back and refer to the <filename>NEWS.Debian</filename> "
-"file after the install. And it's better than listing major changes in "
-"<filename>README.Debian</filename>, since the user can easily miss such "
-"notes."
+"like <systemitem role=\"package\">apt-listchanges</systemitem>, before all "
+"the rest of the changelogs. This is the preferred means to let the user "
+"know about significant changes in a package. It is better than using "
+"<systemitem role=\"package\">debconf</systemitem> notes since it is less "
+"annoying and the user can go back and refer to the "
+"<filename>NEWS.Debian</filename> file after the install. And it's better "
+"than listing major changes in <filename>README.Debian</filename>, since the "
+"user can easily miss such notes."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:1119
msgid ""
"The short description should be kept short (50 characters or so) so that it "
-"may be accomodated by most debconf interfaces. Keeping it short also helps "
+"may be accommodated by most debconf interfaces. Keeping it short also helps "
"translators, as usually translations tend to end up being longer than the "
"original."
msgstr ""
"The short description should be phrased in the form of a question which "
"should be kept short and should generally end with a question mark. Terse "
"writing style is permitted and even encouraged if the question is rather "
-"long (remember that translations are often longer than original versions)"
+"long (remember that translations are often longer than original versions)."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
"the default value for a language choice), consider using the special "
"_Default type documented in <citerefentry> "
"<refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> "
-"</citerefentry>)."
+"</citerefentry>."
msgstr ""
#. type: Content of: <chapter><section><title>
#: best-pkging-practices.dbk:1364
msgid ""
"This section contains global information for developers to make translators' "
-"life easier. More information for translators and developers interrested in "
+"life easier. More information for translators and developers interested in "
"internationalization are available in the <ulink "
"url=\"&url-i18n-l10n;\">Internationalisation and localisation in "
"Debian</ulink> documentation."
"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><section><title>
-#: best-pkging-practices.dbk:1676
-msgid "Best practices for <filename>.orig.tar.{gz,bz2,lzma}</filename> files"
+#: best-pkging-practices.dbk:1683
+msgid "Best practices for <filename>.orig.tar.{gz,bz2,xz}</filename> files"
msgstr ""
#. 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."
msgstr ""
#. 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 "
"upstream notices that he wasn't using maximal compression in his original "
"distribution and then re-<command>gzip</command>s it), that's just too bad. "
"Since there is no good way to upload a new "
-"<filename>.orig.tar.{gz,bz2,lzma}</filename> for the same version, there is "
+"<filename>.orig.tar.{gz,bz2,xz}</filename> for the same version, there is "
"not even any point in treating this situation as a bug."
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 "
+"<filename>.orig.tar.{gz,bz2,xz}</filename> file is byte-for-byte identical "
"to a tarball officially distributed by the upstream author.<placeholder "
"type=\"footnote\" id=\"0\"/> This makes it possible to use checksums to "
"easily verify that all changes between Debian's version and upstream's are "
msgstr ""
#. 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 "
msgstr ""
#. 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>
-#: best-pkging-practices.dbk:1715
+#: best-pkging-practices.dbk:1722
#, no-wrap
msgid ""
"zcat "
msgstr ""
#. 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, "
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1740
+#: best-pkging-practices.dbk:1747
msgid "Repackaged upstream source"
msgstr ""
#. 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 repackaged upstream source. Note that a repackaged upstream "
+"<filename>.orig.tar.{gz,bz2,xz}</filename> file himself. We refer to such a "
+"tarball as a repackaged upstream source. Note that a repackaged upstream "
"source is different from a Debian-native package. A repackaged source still "
"comes with Debian-specific changes in a separate "
"<filename>.diff.gz</filename> or "
-"<filename>.debian.tar.{gz,bz2,lzma}</filename> and still has a version "
-"number composed of <replaceable>upstream-version</replaceable> and "
+"<filename>.debian.tar.{gz,bz2,xz}</filename> and still has a version number "
+"composed of <replaceable>upstream-version</replaceable> and "
"<replaceable>debian-version</replaceable>."
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 "
+"upstream distributes a <filename>.tar.{gz,bz2,xz}</filename> that could in "
"principle be used in its pristine form. The most obvious is if "
"<emphasis>significant</emphasis> space savings can be achieved by "
"recompressing the tar archive or by removing genuinely useless cruft from "
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1767
-msgid "A repackaged <filename>.orig.tar.{gz,bz2,lzma}</filename>"
+#: best-pkging-practices.dbk:1774
+msgid "A repackaged <filename>.orig.tar.{gz,bz2,xz}</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 "
msgstr ""
#. 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-version</replaceable>.orig</filename> "
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 "
msgstr ""
#. 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 "
msgstr ""
#. 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, "
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 "
msgstr ""
#. 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 ""
+
+#. type: Content of: <chapter><section><section><title>
+#: best-pkging-practices.dbk:1908
+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 ""