#. type: Content of: <chapter><para>
#: best-pkging-practices.dbk:9
msgid ""
-"Debian's quality is largely due to the <ulink "
-"url=\"&url-debian-policy;\">Debian Policy</ulink>, which defines explicit "
-"baseline requirements which all Debian packages must fulfill. Yet there is "
-"also a shared history of experience which goes beyond the Debian Policy, an "
-"accumulation of years of experience in packaging. Many very talented people "
-"have created great tools, tools which help you, the Debian maintainer, "
-"create and maintain excellent packages."
+"Debian's quality is largely due to the <ulink url=\"&url-debian-policy;"
+"\">Debian Policy</ulink>, which defines explicit baseline requirements which "
+"all Debian packages must fulfill. Yet there is also a shared history of "
+"experience which goes beyond the Debian Policy, an accumulation of years of "
+"experience in packaging. Many very talented people have created great "
+"tools, tools which help you, the Debian maintainer, create and maintain "
+"excellent packages."
msgstr ""
#. type: Content of: <chapter><para>
#: best-pkging-practices.dbk:52
msgid ""
"<xref linkend=\"tools\"/> contains a couple of different helpers. The most "
-"common and best (in our opinion) helper system is <systemitem "
-"role=\"package\">debhelper</systemitem>. Previous helper systems, such as "
-"<systemitem role=\"package\">debmake</systemitem>, were monolithic: you "
-"couldn't pick and choose which part of the helper you found useful, but had "
-"to use the helper to do everything. <systemitem "
-"role=\"package\">debhelper</systemitem>, however, is a number of separate "
-"little <command>dh_*</command> programs. For instance, "
-"<command>dh_installman</command> installs and compresses man pages, "
-"<command>dh_installmenu</command> installs menu files, and so on. Thus, it "
-"offers enough flexibility to be able to use the little helper scripts, where "
-"useful, in conjunction with hand-crafted commands in "
+"common and best (in our opinion) helper system is <systemitem role=\"package"
+"\">debhelper</systemitem>. Previous helper systems, such as <systemitem "
+"role=\"package\">debmake</systemitem>, were monolithic: you couldn't pick "
+"and choose which part of the helper you found useful, but had to use the "
+"helper to do everything. <systemitem role=\"package\">debhelper</"
+"systemitem>, however, is a number of separate little <command>dh_*</command> "
+"programs. For instance, <command>dh_installman</command> installs and "
+"compresses man pages, <command>dh_installmenu</command> installs menu files, "
+"and so on. Thus, it offers enough flexibility to be able to use the little "
+"helper scripts, where useful, in conjunction with hand-crafted commands in "
"<filename>debian/rules</filename>."
msgstr ""
"by reading <citerefentry> <refentrytitle>debhelper</refentrytitle> "
"<manvolnum>1</manvolnum> </citerefentry>, and looking at the examples that "
"come with the package. <command>dh_make</command>, from the <systemitem "
-"role=\"package\">dh-make</systemitem> package (see <xref "
-"linkend=\"dh-make\"/>), can be used to convert a vanilla source package to a "
-"<systemitem role=\"package\">debhelper</systemitem>ized package. This "
-"shortcut, though, should not convince you that you do not need to bother "
-"understanding the individual <command>dh_*</command> helpers. If you are "
-"going to use a helper, you do need to take the time to learn to use that "
-"helper, to learn its expectations and behavior."
+"role=\"package\">dh-make</systemitem> package (see <xref linkend=\"dh-make\"/"
+">), can be used to convert a vanilla source package to a <systemitem role="
+"\"package\">debhelper</systemitem>ized package. This shortcut, though, "
+"should not convince you that you do not need to bother understanding the "
+"individual <command>dh_*</command> helpers. If you are going to use a "
+"helper, you do need to take the time to learn to use that helper, to learn "
+"its expectations and behavior."
msgstr ""
#. type: Content of: <chapter><section><section><para>
msgid ""
"Fortunately, with the source format “3.0 (quilt)” it is now possible to keep "
"patches separate without having to modify <filename>debian/rules</filename> "
-"to setup a patch system. Patches are stored in "
-"<filename>debian/patches/</filename> and when the source package is unpacked "
-"patches listed in <filename>debian/patches/series</filename> are "
-"automatically applied. As the name implies, patches can be managed with "
-"<command>quilt</command>."
+"to setup a patch system. Patches are stored in <filename>debian/patches/</"
+"filename> and when the source package is unpacked patches listed in "
+"<filename>debian/patches/series</filename> are automatically applied. As "
+"the name implies, patches can be managed with <command>quilt</command>."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:119
msgid ""
"<command>quilt</command> is the recommended tool for this. It does all of "
-"the above, and also allows to manage patch series. See the <systemitem "
-"role=\"package\">quilt</systemitem> package for more information."
+"the above, and also allows to manage patch series. See the <systemitem role="
+"\"package\">quilt</systemitem> package for more information."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:125
msgid ""
"There are other tools to manage patches, like <command>dpatch</command>, and "
-"the patch system integrated with <systemitem "
-"role=\"package\">cdbs</systemitem>."
+"the patch system integrated with <systemitem role=\"package\">cdbs</"
+"systemitem>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:134
msgid ""
"A single source package will often build several binary packages, either to "
-"provide several flavors of the same software (e.g., the <systemitem "
-"role=\"package\">vim</systemitem> source package) or to make several small "
+"provide several flavors of the same software (e.g., the <systemitem role="
+"\"package\">vim</systemitem> source package) or to make several small "
"packages instead of a big one (e.g., so the user can install only the subset "
"needed, and thus save some disk space)."
msgstr ""
msgid ""
"The second case can be easily managed in <filename>debian/rules</filename>. "
"You just need to move the appropriate files from the build directory into "
-"the package's temporary trees. You can do this using "
-"<command>install</command> or <command>dh_install</command> from <systemitem "
-"role=\"package\">debhelper</systemitem>. Be sure to check the different "
-"permutations of the various packages, ensuring that you have the "
-"inter-package dependencies set right in <filename>debian/control</filename>."
+"the package's temporary trees. You can do this using <command>install</"
+"command> or <command>dh_install</command> from <systemitem role=\"package"
+"\">debhelper</systemitem>. Be sure to check the different permutations of "
+"the various packages, ensuring that you have the inter-package dependencies "
+"set right in <filename>debian/control</filename>."
msgstr ""
#. type: Content of: <chapter><section><section><para>
"The first case is a bit more difficult since it involves multiple recompiles "
"of the same software but with different configuration options. The "
"<systemitem role=\"package\">vim</systemitem> source package is an example "
-"of how to manage this using an hand-crafted "
-"<filename>debian/rules</filename> file."
+"of how to manage this using an hand-crafted <filename>debian/rules</"
+"filename> file."
msgstr ""
#. type: Content of: <chapter><section><title>
#. type: Content of: <chapter><section><para>
#: best-pkging-practices.dbk:164
msgid ""
-"The following practices are relevant to the "
-"<filename>debian/control</filename> file. They supplement the <ulink "
-"url=\"&url-debian-policy;ch-binary.html#s-descriptions\">Policy on package "
-"descriptions</ulink>."
+"The following practices are relevant to the <filename>debian/control</"
+"filename> file. They supplement the <ulink url=\"&url-debian-policy;ch-"
+"binary.html#s-descriptions\">Policy on package descriptions</ulink>."
msgstr ""
#. type: Content of: <chapter><section><para>
#: best-pkging-practices.dbk:188
msgid ""
"Our review of package descriptions lead us to conclude that most package "
-"descriptions are technical, that is, are not written to make sense for "
-"non-technical users. Unless your package really is only for technical "
-"users, this is a problem."
+"descriptions are technical, that is, are not written to make sense for non-"
+"technical users. Unless your package really is only for technical users, "
+"this is a problem."
msgstr ""
#. type: Content of: <chapter><section><section><para>
msgid ""
"References to the names of any other software packages, protocol names, "
"standards, or specifications should use their canonical forms, if one "
-"exists. For example, use X Window System, X11, or X; not X Windows, "
-"X-Windows, or X Window. Use GTK+, not GTK or gtk. Use GNOME, not Gnome. "
-"Use PostScript, not Postscript or postscript."
+"exists. For example, use X Window System, X11, or X; not X Windows, X-"
+"Windows, or X Window. Use GTK+, not GTK or gtk. Use GNOME, not Gnome. Use "
+"PostScript, not Postscript or postscript."
msgstr ""
#. type: Content of: <chapter><section><section><para>
msgid ""
"Technically this is a noun phrase minus articles, as opposed to a verb "
"phrase. A good heuristic is that it should be possible to substitute the "
-"package <replaceable>name</replaceable> and "
-"<replaceable>synopsis</replaceable> into this formula:"
+"package <replaceable>name</replaceable> and <replaceable>synopsis</"
+"replaceable> into this formula:"
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:256
msgid ""
"These synopses follow a modified formula. Where a package "
-"\"<replaceable>name</replaceable>\" has a synopsis "
-"\"<replaceable>suite</replaceable> (<replaceable>role</replaceable>)\" or "
-"\"<replaceable>suite</replaceable> - <replaceable>role</replaceable>\", the "
-"elements should be phrased so that they fit into the formula:"
+"\"<replaceable>name</replaceable>\" has a synopsis \"<replaceable>suite</"
+"replaceable> (<replaceable>role</replaceable>)\" or \"<replaceable>suite</"
+"replaceable> - <replaceable>role</replaceable>\", the elements should be "
+"phrased so that they fit into the formula:"
msgstr ""
#. type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:294
msgid ""
-"Be careful to avoid spelling and grammar mistakes. Ensure that you "
-"spell-check it. Both <command>ispell</command> and "
-"<command>aspell</command> have special modes for checking "
-"<filename>debian/control</filename> files:"
+"Be careful to avoid spelling and grammar mistakes. Ensure that you spell-"
+"check it. Both <command>ispell</command> and <command>aspell</command> have "
+"special modes for checking <filename>debian/control</filename> files:"
msgstr ""
#. type: Content of: <chapter><section><section><screen>
"<literal>cvs</literal>, <literal>darcs</literal>, <literal>git</literal>, "
"<literal>hg</literal> (Mercurial), <literal>mtn</literal> (Monotone), "
"<literal>svn</literal> (Subversion). It is allowed to specify different VCS "
-"fields for the same package: they will all be shown in the PTS web "
-"interface."
+"fields for the same package: they will all be shown in the PTS web interface."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
"In the following example, an instance of the field for a Subversion "
"repository of the <systemitem role=\"package\">vim</systemitem> package is "
"shown. Note how the URL is in the <literal>svn://</literal> scheme (instead "
-"of <literal>svn+ssh://</literal>) and how it points to the "
-"<filename>trunk/</filename> branch. The use of the "
-"<literal>Vcs-Browser</literal> and <literal>Homepage</literal> fields "
-"described above is also shown."
+"of <literal>svn+ssh://</literal>) and how it points to the <filename>trunk/</"
+"filename> branch. The use of the <literal>Vcs-Browser</literal> and "
+"<literal>Homepage</literal> fields described above is also shown."
msgstr ""
#. type: Content of: <chapter><section><section><section><screen>
#. type: Content of: <chapter><section><para>
#: best-pkging-practices.dbk:429
msgid ""
-"The following practices supplement the <ulink "
-"url=\"&url-debian-policy;ch-docs.html#s-changelogs\">Policy on changelog "
-"files</ulink>."
+"The following practices supplement the <ulink url=\"&url-debian-policy;ch-"
+"docs.html#s-changelogs\">Policy on changelog files</ulink>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:436
msgid ""
"The changelog entry for a package revision documents changes in that "
-"revision, and only them. Concentrate on describing significant and "
-"user-visible changes that were made since the last version."
+"revision, and only them. Concentrate on describing significant and user-"
+"visible changes that were made since the last version."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:466
msgid ""
"When referring to bugs, don't assume anything. Say what the problem was, "
-"how it was fixed, and append the closes: #nnnnn string. See <xref "
-"linkend=\"upload-bugfix\"/> for more information."
+"how it was fixed, and append the closes: #nnnnn string. See <xref linkend="
+"\"upload-bugfix\"/> for more information."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:568
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 <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."
+"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 "
+"<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>
"rather than the more concise summaries that would go in a changelog. It's a "
"good idea to run your file through <literal>dpkg-parsechangelog</literal> to "
"check its formatting as it will not be automatically checked during build as "
-"the changelog is. Here is an example of a real "
-"<filename>NEWS.Debian</filename> file:"
+"the changelog is. Here is an example of a real <filename>NEWS.Debian</"
+"filename> file:"
msgstr ""
#. type: Content of: <chapter><section><section><screen>
" functionality provided with that script, please install the new\n"
" package.\n"
"\n"
-" -- Steve Greenland <stevegr@debian.org> Sat, 6 Sep 2003 17:15:03 "
-"-0500\n"
+" -- Steve Greenland <stevegr@debian.org> Sat, 6 Sep 2003 17:15:03 -0500\n"
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:598
msgid ""
-"The <filename>NEWS.Debian</filename> file is installed as "
-"<filename>/usr/share/doc/<replaceable>package</replaceable>/NEWS.Debian.gz</filename>. "
-"It is compressed, and always has that name even in Debian native packages. "
-"If you use <literal>debhelper</literal>, "
-"<literal>dh_installchangelogs</literal> will install "
-"<filename>debian/NEWS</filename> files for you."
+"The <filename>NEWS.Debian</filename> file is installed as <filename>/usr/"
+"share/doc/<replaceable>package</replaceable>/NEWS.Debian.gz</filename>. It "
+"is compressed, and always has that name even in Debian native packages. If "
+"you use <literal>debhelper</literal>, <literal>dh_installchangelogs</"
+"literal> will install <filename>debian/NEWS</filename> files for you."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:646
msgid ""
"All prompting or interactive configuration should be kept to a minimum. "
-"When it is necessary, you should use the <systemitem "
-"role=\"package\">debconf</systemitem> package for the interface. Remember "
-"that prompting in any case can only be in the <literal>configure</literal> "
-"stage of the <filename>postinst</filename> script."
+"When it is necessary, you should use the <systemitem role=\"package"
+"\">debconf</systemitem> package for the interface. Remember that prompting "
+"in any case can only be in the <literal>configure</literal> stage of the "
+"<filename>postinst</filename> script."
msgstr ""
#. type: Content of: <chapter><section><para>
"Keep the maintainer scripts as simple as possible. We suggest you use pure "
"POSIX shell scripts. Remember, if you do need any bash features, the "
"maintainer script must have a bash shebang line. POSIX shell or Bash are "
-"preferred to Perl, since they enable <systemitem "
-"role=\"package\">debhelper</systemitem> to easily add bits to the scripts."
+"preferred to Perl, since they enable <systemitem role=\"package\">debhelper</"
+"systemitem> to easily add bits to the scripts."
msgstr ""
#. type: Content of: <chapter><section><para>
"You can use this function to search <varname>$PATH</varname> for a command "
"name, passed as an argument. It returns true (zero) if the command was "
"found, and false if not. This is really the most portable way, since "
-"<literal>command -v</literal>, <command>type</command>, and "
-"<command>which</command> are not POSIX."
+"<literal>command -v</literal>, <command>type</command>, and <command>which</"
+"command> are not POSIX."
msgstr ""
#. type: Content of: <chapter><section><para>
msgid ""
"While <command>which</command> is an acceptable alternative, since it is "
"from the required <systemitem role=\"package\">debianutils</systemitem> "
-"package, it's not on the root partition. That is, it's in "
-"<filename>/usr/bin</filename> rather than <filename>/bin</filename>, so one "
-"can't use it in scripts which are run before the <filename>/usr</filename> "
-"partition is mounted. Most scripts won't have this problem, though."
+"package, it's not on the root partition. That is, it's in <filename>/usr/"
+"bin</filename> rather than <filename>/bin</filename>, so one can't use it in "
+"scripts which are run before the <filename>/usr</filename> partition is "
+"mounted. Most scripts won't have this problem, though."
msgstr ""
#. type: Content of: <chapter><section><title>
#: best-pkging-practices.dbk:693
msgid ""
-"Configuration management with <systemitem "
-"role=\"package\">debconf</systemitem>"
+"Configuration management with <systemitem role=\"package\">debconf</"
+"systemitem>"
msgstr ""
#. type: Content of: <chapter><section><para>
#: best-pkging-practices.dbk:703
msgid ""
"Debconf is a great tool but it is often poorly used. Many common mistakes "
-"are listed in the <citerefentry> "
-"<refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</manvolnum> "
-"</citerefentry> man page. It is something that you must read if you decide "
-"to use debconf. Also, we document some best practices here."
+"are listed in the <citerefentry> <refentrytitle>debconf-devel</"
+"refentrytitle> <manvolnum>7</manvolnum> </citerefentry> man page. It is "
+"something that you must read if you decide to use debconf. Also, we "
+"document some best practices here."
msgstr ""
#. type: Content of: <chapter><section><para>
#: best-pkging-practices.dbk:730
msgid ""
"Carefully choose the questions priorities in maintainer scripts. See "
-"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> "
-"<manvolnum>7</manvolnum> </citerefentry> for details about priorities. Most "
-"questions should use medium and low priorities."
+"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</"
+"manvolnum> </citerefentry> for details about priorities. Most questions "
+"should use medium and low priorities."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:750
msgid ""
-"Badly written templates give a poor image of your package, of your "
-"work... or even of Debian itself."
+"Badly written templates give a poor image of your package, of your work... "
+"or even of Debian itself."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:769
msgid ""
-"Please use gettext-based templates. Install <systemitem "
-"role=\"package\">po-debconf</systemitem> on your development system and read "
-"its documentation (<command>man po-debconf</command> is a good start)."
+"Please use gettext-based templates. Install <systemitem role=\"package\">po-"
+"debconf</systemitem> on your development system and read its documentation "
+"(<command>man po-debconf</command> is a good start)."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:782
msgid ""
"If you plan to do changes to your original templates, please use the "
-"notification system provided with the <systemitem "
-"role=\"package\">po-debconf</systemitem> package, namely the "
-"<command>podebconf-report-po</command>, to contact translators. Most active "
-"translators are very responsive and getting their work included along with "
-"your modified templates will save you additional uploads. If you use "
-"gettext-based templates, the translator's name and e-mail addresses are "
-"mentioned in the PO files headers and will be used by "
-"<command>podebconf-report-po</command>."
+"notification system provided with the <systemitem role=\"package\">po-"
+"debconf</systemitem> package, namely the <command>podebconf-report-po</"
+"command>, to contact translators. Most active translators are very "
+"responsive and getting their work included along with your modified "
+"templates will save you additional uploads. If you use gettext-based "
+"templates, the translator's name and e-mail addresses are mentioned in the "
+"PO files headers and will be used by <command>podebconf-report-po</command>."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><programlisting>
#: best-pkging-practices.dbk:796
#, no-wrap
-msgid ""
-"cd debian/po && podebconf-report-po --call --languageteam "
-"--withtranslators --deadline=\"+10 days\""
+msgid "cd debian/po && podebconf-report-po --call --languageteam --withtranslators --deadline=\"+10 days\""
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:798
msgid ""
-"This command will first synchronize the PO and POT files in "
-"<filename>debian/po</filename> with the templates files listed in "
-"<filename>debian/po/POTFILES.in</filename>. Then, it will send a call for "
-"new translations, in the &email-debian-i18n; mailing list. Finally, it will "
-"also send a call for translation updates to the language team (mentioned in "
-"the <literal>Language-Team</literal> field of each PO file) as well as the "
-"last translator (mentioned in <literal>Last-translator</literal>)."
+"This command will first synchronize the PO and POT files in <filename>debian/"
+"po</filename> with the templates files listed in <filename>debian/po/"
+"POTFILES.in</filename>. Then, it will send a call for new translations, in "
+"the &email-debian-i18n; mailing list. Finally, it will also send a call for "
+"translation updates to the language team (mentioned in the <literal>Language-"
+"Team</literal> field of each PO file) as well as the last translator "
+"(mentioned in <literal>Last-translator</literal>)."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:823
msgid ""
-"When the text of a debconf template is corrected and you are <emphasis "
-"role=\"strong\">sure</emphasis> that the change does <emphasis "
-"role=\"strong\">not</emphasis> affect translations, please be kind to "
-"translators and <emphasis>unfuzzy</emphasis> their translations."
+"When the text of a debconf template is corrected and you are <emphasis role="
+"\"strong\">sure</emphasis> that the change does <emphasis role=\"strong"
+"\">not</emphasis> affect translations, please be kind to translators and "
+"<emphasis>unfuzzy</emphasis> their translations."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
#: best-pkging-practices.dbk:844
msgid ""
-"Try finding a complete translation file <emphasis "
-"role=\"strong\">before</emphasis> the change:"
+"Try finding a complete translation file <emphasis role=\"strong\">before</"
+"emphasis> the change:"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
#: best-pkging-practices.dbk:847 best-pkging-practices.dbk:918
#, no-wrap
-msgid ""
-"for i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null --statistics "
-"$i; done"
+msgid "for i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null --statistics $i; done"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
#: best-pkging-practices.dbk:962
msgid ""
"Templates text should not make reference to widgets belonging to some "
-"debconf interfaces. Sentences like <emphasis>If you answer "
-"Yes...</emphasis> have no meaning for users of graphical interfaces which "
-"use checkboxes for boolean questions."
+"debconf interfaces. Sentences like <emphasis>If you answer Yes...</"
+"emphasis> have no meaning for users of graphical interfaces which use "
+"checkboxes for boolean questions."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:981
msgid ""
-"You should avoid the use of first person (<emphasis>I will do "
-"this...</emphasis> or <emphasis>We recommend...</emphasis>). The computer "
-"is not a person and the Debconf templates do not speak for the Debian "
-"developers. You should use neutral construction. Those of you who already "
-"wrote scientific publications, just write your templates like you would "
-"write a scientific paper. However, try using active voice if still "
-"possible, like <emphasis>Enable this if ...</emphasis> instead of "
-"<emphasis>This can be enabled if...</emphasis>."
+"You should avoid the use of first person (<emphasis>I will do this...</"
+"emphasis> or <emphasis>We recommend...</emphasis>). The computer is not a "
+"person and the Debconf templates do not speak for the Debian developers. "
+"You should use neutral construction. Those of you who already wrote "
+"scientific publications, just write your templates like you would write a "
+"scientific paper. However, try using active voice if still possible, like "
+"<emphasis>Enable this if ...</emphasis> instead of <emphasis>This can be "
+"enabled if...</emphasis>."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
#: best-pkging-practices.dbk:1003
msgid ""
"This part gives some information which is mostly taken from the "
-"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> "
-"<manvolnum>7</manvolnum> </citerefentry> manual page."
+"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</"
+"manvolnum> </citerefentry> manual page."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
#. type: Content of: <chapter><section><section><section><section><para>
#: best-pkging-practices.dbk:1012
-msgid "Results in a free-form input field that the user can type any string into."
+msgid ""
+"Results in a free-form input field that the user can type any string into."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
#: best-pkging-practices.dbk:1064
msgid ""
"The debconf templates flag system offers many such possibilities. The "
-"<citerefentry> <refentrytitle>po-debconf</refentrytitle> "
-"<manvolnum>7</manvolnum> </citerefentry> manual page lists all these "
-"possibilities."
+"<citerefentry> <refentrytitle>po-debconf</refentrytitle> <manvolnum>7</"
+"manvolnum> </citerefentry> manual page lists all these possibilities."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><title>
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
#: best-pkging-practices.dbk:1203
msgid ""
-"The short description is a prompt and <emphasis "
-"role=\"strong\">not</emphasis> a title. Avoid question style prompts (IP "
-"Address?) in favour of opened prompts (IP address:). The use of colons is "
-"recommended."
+"The short description is a prompt and <emphasis role=\"strong\">not</"
+"emphasis> a title. Avoid question style prompts (IP Address?) in favour of "
+"opened prompts (IP address:). The use of colons is recommended."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
#: best-pkging-practices.dbk:1244
msgid ""
-"The short description is a prompt and <emphasis "
-"role=\"strong\">not</emphasis> a title. Do <emphasis "
-"role=\"strong\">not</emphasis> use useless Please choose... constructions. "
-"Users are clever enough to figure out they have to choose something...:)"
+"The short description is a prompt and <emphasis role=\"strong\">not</"
+"emphasis> a title. Do <emphasis role=\"strong\">not</emphasis> use useless "
+"Please choose... constructions. Users are clever enough to figure out they "
+"have to choose something...:)"
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
#: best-pkging-practices.dbk:1266
msgid ""
-"The short description should be considered to be a <emphasis "
-"role=\"strong\">title</emphasis>."
+"The short description should be considered to be a <emphasis role=\"strong"
+"\">title</emphasis>."
msgstr ""
#. type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
"it's best to use them only for warning about very serious problems. The "
"<filename>NEWS.Debian</filename> or <filename>README.Debian</filename> files "
"are the appropriate location for a lot of notes. If, by reading this, you "
-"consider converting your Note type templates to entries in "
-"<filename>NEWS.Debian</filename> or <filename>README.Debian</filename>, plus "
-"consider keeping existing translations for the future."
+"consider converting your Note type templates to entries in <filename>NEWS."
+"Debian</filename> or <filename>README.Debian</filename>, plus consider "
+"keeping existing translations for the future."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
msgid ""
"Template: geneweb/lang\n"
"Type: select\n"
-"__Choices: Afrikaans (af), Bulgarian (bg), Catalan (ca), Chinese (zh), Czech "
-"(cs), Danish (da), Dutch (nl), English (en), Esperanto (eo), Estonian (et), "
-"Finnish (fi), French (fr), German (de), Hebrew (he), Icelandic (is), Italian "
-"(it), Latvian (lv), Norwegian (no), Polish (pl), Portuguese (pt), Romanian "
-"(ro), Russian (ru), Spanish (es), Swedish (sv)\n"
+"__Choices: Afrikaans (af), Bulgarian (bg), Catalan (ca), Chinese (zh), Czech (cs), Danish (da), Dutch (nl), English (en), Esperanto (eo), Estonian (et), Finnish (fi), French (fr), German (de), Hebrew (he), Icelandic (is), Italian (it), Latvian (lv), Norwegian (no), Polish (pl), Portuguese (pt), Romanian (ro), Russian (ru), Spanish (es), Swedish (sv)\n"
"# This is the default choice. Translators may put their own language here\n"
"# instead of the default.\n"
"# WARNING : you MUST use the ENGLISH NAME of your language\n"
msgid ""
"If the default value may vary depending on language/country (for instance "
"the default value for a language choice), consider using the special "
-"_Default type documented in <citerefentry> "
-"<refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> "
-"</citerefentry>)."
+"_Default type documented in <citerefentry> <refentrytitle>po-debconf</"
+"refentrytitle> <manvolnum>7</manvolnum> </citerefentry>)."
msgstr ""
#. type: Content of: <chapter><section><title>
msgid ""
"This section contains global information for developers to make translators' "
"life easier. More information for translators and developers interrested in "
-"internationalization are available in the <ulink "
-"url=\"&url-i18n-l10n;\">Internationalisation and localisation in "
-"Debian</ulink> documentation."
+"internationalization are available in the <ulink url=\"&url-i18n-l10n;"
+"\">Internationalisation and localisation in Debian</ulink> documentation."
msgstr ""
#. type: Content of: <chapter><section><section><title>
msgid ""
"The goal of <systemitem role=\"package\">debconf</systemitem> was to make "
"packages configuration easier for maintainers and for users. Originally, "
-"translation of debconf templates was handled with "
-"<command>debconf-mergetemplate</command>. However, that technique is now "
-"deprecated; the best way to accomplish <systemitem "
-"role=\"package\">debconf</systemitem> internationalization is by using the "
-"<systemitem role=\"package\">po-debconf</systemitem> package. This method "
-"is easier both for maintainer and translators; transition scripts are "
-"provided."
+"translation of debconf templates was handled with <command>debconf-"
+"mergetemplate</command>. However, that technique is now deprecated; the "
+"best way to accomplish <systemitem role=\"package\">debconf</systemitem> "
+"internationalization is by using the <systemitem role=\"package\">po-"
+"debconf</systemitem> package. This method is easier both for maintainer and "
+"translators; transition scripts are provided."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:1389
msgid ""
"Using <systemitem role=\"package\">po-debconf</systemitem>, the translation "
-"is stored in <filename>.po</filename> files (drawing from "
-"<command>gettext</command> translation techniques). Special template files "
-"contain the original messages and mark which fields are translatable. When "
-"you change the value of a translatable field, by calling "
-"<command>debconf-updatepo</command>, the translation is marked as needing "
-"attention from the translators. Then, at build time, the "
-"<command>dh_installdebconf</command> program takes care of all the needed "
-"magic to add the template along with the up-to-date translations into the "
-"binary packages. Refer to the <citerefentry> "
-"<refentrytitle>po-debconf</refentrytitle> <manvolnum>7</manvolnum> "
-"</citerefentry> manual page for details."
+"is stored in <filename>.po</filename> files (drawing from <command>gettext</"
+"command> translation techniques). Special template files contain the "
+"original messages and mark which fields are translatable. When you change "
+"the value of a translatable field, by calling <command>debconf-updatepo</"
+"command>, the translation is marked as needing attention from the "
+"translators. Then, at build time, the <command>dh_installdebconf</command> "
+"program takes care of all the needed magic to add the template along with "
+"the up-to-date translations into the binary packages. Refer to the "
+"<citerefentry> <refentrytitle>po-debconf</refentrytitle> <manvolnum>7</"
+"manvolnum> </citerefentry> manual page for details."
msgstr ""
#. type: Content of: <chapter><section><section><title>
"they can see what needs to be retranslated. It is recommended that the "
"translated documentation maintain a note about what source control revision "
"the translation is based on. An interesting system is provided by <ulink "
-"url=\"&url-i18n-doc-check;\">doc-check</ulink> in the <systemitem "
-"role=\"package\">debian-installer</systemitem> package, which shows an "
-"overview of the translation status for any given language, using structured "
-"comments for the current revision of the file to be translated and, for a "
-"translated file, the revision of the original file the translation is based "
-"on. You might wish to adapt and provide that in your VCS area."
+"url=\"&url-i18n-doc-check;\">doc-check</ulink> in the <systemitem role="
+"\"package\">debian-installer</systemitem> package, which shows an overview "
+"of the translation status for any given language, using structured comments "
+"for the current revision of the file to be translated and, for a translated "
+"file, the revision of the original file the translation is based on. You "
+"might wish to adapt and provide that in your VCS area."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:1432
msgid ""
"Some tools (e.g. <systemitem role=\"package\">po4a</systemitem>, <systemitem "
-"role=\"package\">poxml</systemitem>, or the <systemitem "
-"role=\"package\">translate-toolkit</systemitem>) are specialized in "
-"extracting the translatable material from different formats. They produce "
-"PO files, a format quite common to translators, which permits to see what "
-"needs to be retranslated when the translated document is updated."
+"role=\"package\">poxml</systemitem>, or the <systemitem role=\"package"
+"\">translate-toolkit</systemitem>) are specialized in extracting the "
+"translatable material from different formats. They produce PO files, a "
+"format quite common to translators, which permits to see what needs to be "
+"retranslated when the translated document is updated."
msgstr ""
#. type: Content of: <chapter><section><title>
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:1477
msgid ""
-"Good practices for library packaging have been grouped in <ulink "
-"url=\"&url-libpkg-guide;\">the library packaging guide</ulink>."
+"Good practices for library packaging have been grouped in <ulink url=\"&url-"
+"libpkg-guide;\">the library packaging guide</ulink>."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:1503
msgid ""
-"Major shipped manuals should register themselves with <systemitem "
-"role=\"package\">doc-base</systemitem> on installation. See the <systemitem "
-"role=\"package\">doc-base</systemitem> package documentation for more "
-"information."
+"Major shipped manuals should register themselves with <systemitem role="
+"\"package\">doc-base</systemitem> on installation. See the <systemitem role="
+"\"package\">doc-base</systemitem> package documentation for more information."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
#: best-pkging-practices.dbk:1533
msgid ""
-"Perl related packages have a <ulink url=\"&url-perl-policy;\">Perl "
-"policy</ulink>, some examples of packages following that policy are "
-"<systemitem role=\"package\">libdbd-pg-perl</systemitem> (binary perl "
-"module) or <systemitem role=\"package\">libmldbm-perl</systemitem> (arch "
-"independent perl module)."
+"Perl related packages have a <ulink url=\"&url-perl-policy;\">Perl policy</"
+"ulink>, some examples of packages following that policy are <systemitem role="
+"\"package\">libdbd-pg-perl</systemitem> (binary perl module) or <systemitem "
+"role=\"package\">libmldbm-perl</systemitem> (arch independent perl module)."
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
#: best-pkging-practices.dbk:1571
msgid ""
"Packages providing XML or SGML DTDs should conform to the recommendations "
-"found in the <systemitem role=\"package\">sgml-base-doc</systemitem> "
-"package."
+"found in the <systemitem role=\"package\">sgml-base-doc</systemitem> package."
msgstr ""
#. type: Content of: <chapter><section><section><itemizedlist><listitem><para>
#: best-pkging-practices.dbk:1577
msgid ""
-"Lisp packages should register themselves with <systemitem "
-"role=\"package\">common-lisp-controller</systemitem>, about which see "
-"&file-lisp-controller;."
+"Lisp packages should register themselves with <systemitem role=\"package"
+"\">common-lisp-controller</systemitem>, about which see &file-lisp-"
+"controller;."
msgstr ""
#. type: Content of: <chapter><section><section><title>
#: best-pkging-practices.dbk:1616
msgid ""
"However, if the size of the data is considerable, consider splitting it out "
-"into a separate, architecture-independent package "
-"(<filename>_all.deb</filename>). By doing this, you avoid needless "
-"duplication of the same data into eleven or more .debs, one per each "
-"architecture. While this adds some extra overhead into the "
-"<filename>Packages</filename> files, it saves a lot of disk space on Debian "
-"mirrors. Separating out architecture-independent data also reduces "
-"processing time of <command>lintian</command> (see <xref "
+"into a separate, architecture-independent package (<filename>_all.deb</"
+"filename>). By doing this, you avoid needless duplication of the same data "
+"into eleven or more .debs, one per each architecture. While this adds some "
+"extra overhead into the <filename>Packages</filename> files, it saves a lot "
+"of disk space on Debian mirrors. Separating out architecture-independent "
+"data also reduces processing time of <command>lintian</command> (see <xref "
"linkend=\"tools-lint\"/>) when run over the entire Debian archive."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:1634
msgid ""
-"If you set <varname>LOCPATH</varname> to the equivalent of "
-"<filename>/usr/lib/locale</filename>, and <varname>LC_ALL</varname> to the "
-"name of the locale you generate, you should get what you want without being "
-"root. Something like this:"
+"If you set <varname>LOCPATH</varname> to the equivalent of <filename>/usr/"
+"lib/locale</filename>, and <varname>LC_ALL</varname> to the name of the "
+"locale you generate, you should get what you want without being root. "
+"Something like this:"
msgstr ""
#. type: Content of: <chapter><section><section><screen>
"LOCALE_CHARSET=UTF-8\n"
"\n"
"mkdir -p $LOCALE_PATH\n"
-"localedef -i $LOCALE_NAME.$LOCALE_CHARSET -f $LOCALE_CHARSET "
-"$LOCALE_PATH/$LOCALE_NAME.$LOCALE_CHARSET\n"
+"localedef -i $LOCALE_NAME.$LOCALE_CHARSET -f $LOCALE_CHARSET $LOCALE_PATH/$LOCALE_NAME.$LOCALE_CHARSET\n"
"\n"
"# Using the locale\n"
"LOCPATH=$LOCALE_PATH LC_ALL=$LOCALE_NAME.$LOCALE_CHARSET date\n"
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:1661
msgid ""
-"For example, with <literal>--guess-dummy</literal>, "
-"<command>deborphan</command> tries to search all transitional packages which "
-"were needed for upgrade but which can now safely be removed. For that, it "
-"looks for the string dummy or transitional in their short description."
+"For example, with <literal>--guess-dummy</literal>, <command>deborphan</"
+"command> tries to search all transitional packages which were needed for "
+"upgrade but which can now safely be removed. For that, it looks for the "
+"string dummy or transitional in their short description."
msgstr ""
#. type: Content of: <chapter><section><section><para>
msgid ""
"We cannot prevent upstream authors from changing the tarball they distribute "
"without also incrementing the version number, so there can be no guarantee "
-"that a pristine tarball is identical to what upstream "
-"<emphasis>currently</emphasis> distributing at any point in time. All that "
-"can be expected is that it is identical to something that upstream once "
-"<emphasis>did</emphasis> distribute. If a difference arises later (say, if "
-"upstream notices that he wasn't using maximal compression in his original "
+"that a pristine tarball is identical to what upstream <emphasis>currently</"
+"emphasis> distributing at any point in time. All that can be expected is "
+"that it is identical to something that upstream once <emphasis>did</"
+"emphasis> distribute. If a difference arises later (say, if 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 "
-"not even any point in treating this situation as a bug."
+"Since there is no good way to upload a new <filename>.orig.tar.{gz,bz2,lzma}"
+"</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>
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 "
-"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 "
+"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 "
"contained in the Debian diff. Also, if the original source is huge, "
"upstream authors and others who already have the upstream tarball can save "
"download time if they want to inspect your packaging in detail."
#: best-pkging-practices.dbk:1704
msgid ""
"There is no universally accepted guidelines that upstream authors follow "
-"regarding to the directory structure inside their tarball, but "
-"<command>dpkg-source</command> is nevertheless able to deal with most "
-"upstream tarballs as pristine source. Its strategy is equivalent to the "
-"following:"
+"regarding to the directory structure inside their tarball, but <command>dpkg-"
+"source</command> is nevertheless able to deal with most upstream tarballs as "
+"pristine source. Its strategy is equivalent to the following:"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><screen>
#: best-pkging-practices.dbk:1715
#, no-wrap
-msgid ""
-"zcat "
-"path/to/<replaceable>packagename</replaceable>_<replaceable>upstream-version</replaceable>.orig.tar.gz "
-"| tar xf -\n"
+msgid "zcat path/to/<replaceable>packagename</replaceable>_<replaceable>upstream-version</replaceable>.orig.tar.gz | tar xf -\n"
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
msgid ""
"If, after this, the temporary directory contains nothing but one directory "
"and no other files, <command>dpkg-source</command> renames that directory to "
-"<filename><replaceable>packagename</replaceable>-<replaceable>upstream-version</replaceable>(.orig)</filename>. "
-"The name of the top-level directory in the tarball does not matter, and is "
-"forgotten."
+"<filename><replaceable>packagename</replaceable>-<replaceable>upstream-"
+"version</replaceable>(.orig)</filename>. The name of the top-level "
+"directory in the tarball does not matter, and is forgotten."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
#: best-pkging-practices.dbk:1729
msgid ""
-"Otherwise, the upstream tarball must have been packaged without a common "
-"top-level directory (shame on the upstream author!). In this case, "
+"Otherwise, the upstream tarball must have been packaged without a common top-"
+"level directory (shame on the upstream author!). In this case, "
"<command>dpkg-source</command> renames the temporary directory "
-"<emphasis>itself</emphasis> to "
-"<filename><replaceable>packagename</replaceable>-<replaceable>upstream-version</replaceable>(.orig)</filename>."
+"<emphasis>itself</emphasis> to <filename><replaceable>packagename</"
+"replaceable>-<replaceable>upstream-version</replaceable>(.orig)</filename>."
msgstr ""
#. type: Content of: <chapter><section><section><section><title>
"You <emphasis role=\"strong\">should</emphasis> upload packages with a "
"pristine source tarball if possible, but there are various reasons why it "
"might not be possible. This is the case if upstream does not distribute the "
-"source as gzipped tar at all, or if upstream's tarball contains "
-"non-DFSG-free material that you must remove before uploading."
+"source as gzipped tar at all, or if upstream's tarball contains non-DFSG-"
+"free material that you must remove before uploading."
msgstr ""
#. type: Content of: <chapter><section><section><section><para>
#: best-pkging-practices.dbk:1749
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 "
-"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 "
+"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 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 "
"<replaceable>debian-version</replaceable>."
"source package. Detailed information on how the repackaged source was "
"obtained, and on how this can be reproduced should be provided in "
"<filename>debian/copyright</filename>. It is also a good idea to provide a "
-"<literal>get-orig-source</literal> target in your "
-"<filename>debian/rules</filename> file that repeats the process, as "
-"described in the Policy Manual, <ulink "
-"url=\"&url-debian-policy;ch-source.html#s-debianrules\">Main building "
+"<literal>get-orig-source</literal> target in your <filename>debian/rules</"
+"filename> file that repeats the process, as described in the Policy Manual, "
+"<ulink url=\"&url-debian-policy;ch-source.html#s-debianrules\">Main building "
"script: <filename>debian/rules</filename></ulink>."
msgstr ""
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 "
-"mirror rather than trying to locate a canonical upstream distribution "
-"point)."
+"mirror rather than trying to locate a canonical upstream distribution point)."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
#: best-pkging-practices.dbk:1814
msgid ""
"<emphasis role=\"strong\">should</emphasis> use "
-"<filename><replaceable>packagename</replaceable>-<replaceable>upstream-version</replaceable>.orig</filename> "
-"as the name of the top-level directory in its tarball. This makes it "
-"possible to distinguish pristine tarballs from repackaged ones."
+"<filename><replaceable>packagename</replaceable>-<replaceable>upstream-"
+"version</replaceable>.orig</filename> as the name of the top-level directory "
+"in its tarball. This makes it possible to distinguish pristine tarballs "
+"from repackaged ones."
msgstr ""
#. type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
"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 "
"when using source packages in “3.0 (quilt)” format, see the "
-"<citerefentry><refentrytitle>dpkg-source</refentrytitle><manvolnum>1</manvolnum></citerefentry> "
-"manual page for details. When using the older format “1.0”, binary files "
-"can't be stored in the <filename>.diff.gz</filename> so you must store an "
-"<command>uuencode</command>d (or similar) version of the file(s) and decode "
-"it at build time in <filename>debian/rules</filename> (and move it in its "
-"official location)."
+"<citerefentry><refentrytitle>dpkg-source</refentrytitle><manvolnum>1</"
+"manvolnum></citerefentry> manual page for details. When using the older "
+"format “1.0”, binary files can't be stored in the <filename>.diff.gz</"
+"filename> so you must store an <command>uuencode</command>d (or similar) "
+"version of the file(s) and decode it at build time in <filename>debian/"
+"rules</filename> (and move it in its official location)."
msgstr ""
#. type: Content of: <chapter><section><section><title>
"library or other binary, but most of them can save space and build time by "
"instead containing separated debugging symbols that <command>gdb</command> "
"can find and load on the fly when debugging a program or library. The "
-"convention in Debian is to keep these symbols in "
-"<filename>/usr/lib/debug/<replaceable>path</replaceable></filename>, where "
-"<replaceable>path</replaceable> is the path to the executable or library. "
-"For example, debugging symbols for <filename>/usr/bin/foo</filename> go in "
-"<filename>/usr/lib/debug/usr/bin/foo</filename>, and debugging symbols for "
-"<filename>/usr/lib/libfoo.so.1</filename> go in "
-"<filename>/usr/lib/debug/usr/lib/libfoo.so.1</filename>."
+"convention in Debian is to keep these symbols in <filename>/usr/lib/debug/"
+"<replaceable>path</replaceable></filename>, where <replaceable>path</"
+"replaceable> is the path to the executable or library. For example, "
+"debugging symbols for <filename>/usr/bin/foo</filename> go in <filename>/usr/"
+"lib/debug/usr/bin/foo</filename>, and debugging symbols for <filename>/usr/"
+"lib/libfoo.so.1</filename> go in <filename>/usr/lib/debug/usr/lib/libfoo."
+"so.1</filename>."
msgstr ""
#. type: Content of: <chapter><section><section><para>
"<command>objcopy --only-keep-debug</command>. Then the object file can be "
"stripped, and <command>objcopy --add-gnu-debuglink</command> used to specify "
"the path to the debugging symbol file. <citerefentry> "
-"<refentrytitle>objcopy</refentrytitle> <manvolnum>1</manvolnum> "
-"</citerefentry> explains in detail how this works."
+"<refentrytitle>objcopy</refentrytitle> <manvolnum>1</manvolnum> </"
+"citerefentry> explains in detail how this works."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:1886
msgid ""
-"The <command>dh_strip</command> command in <systemitem "
-"role=\"package\">debhelper</systemitem> supports creating debug packages, "
-"and can take care of using <command>objcopy</command> to separate out the "
-"debugging symbols for you. If your package uses <systemitem "
-"role=\"package\">debhelper</systemitem>, all you need to do is call "
-"<command>dh_strip --dbg-package=libfoo-dbg</command>, and add an entry to "
-"<filename>debian/control</filename> for the debug package."
+"The <command>dh_strip</command> command in <systemitem role=\"package"
+"\">debhelper</systemitem> supports creating debug packages, and can take "
+"care of using <command>objcopy</command> to separate out the debugging "
+"symbols for you. If your package uses <systemitem role=\"package"
+"\">debhelper</systemitem>, all you need to do is call <command>dh_strip --"
+"dbg-package=libfoo-dbg</command>, and add an entry to <filename>debian/"
+"control</filename> for the debug package."
msgstr ""
#. type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:1893
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:"
+"debugging symbols for, and this dependency should be versioned. For example:"
msgstr ""
#. type: Content of: <chapter><section><section><screen>
~ianmdlvl / developers-reference.git / blobdiff