# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
+# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-07-01 21:01+0000\n"
+"POT-Creation-Date: 2008-08-08 11:33-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"
"The rationale for using helper scripts in <filename>debian/rules</filename> "
"is that they let maintainers use and share common logic among many "
"packages. Take for instance the question of installing menu entries: you "
-"need to put the file into <filename>/usr/lib/menu</filename> (or "
+"need to put the file into <filename>/usr/share/menu</filename> (or "
"<filename>/usr/lib/menu</filename> for executable binary menufiles, if this "
"is needed), and add commands to the maintainer scripts to register and "
"unregister the menu entries. Since this is a very common thing for packages "
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:230
+#: best-pkging-practices.dbk:229
#, no-wrap
msgid ""
+"\n"
"<replaceable>package-name</replaceable> is a "
-"<replaceable>synopsis</replaceable>."
+"<replaceable>synopsis</replaceable>.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:236
+#: best-pkging-practices.dbk:235
#, no-wrap
msgid ""
+"\n"
"<replaceable>package-name</replaceable> is "
-"<replaceable>synopsis</replaceable>."
+"<replaceable>synopsis</replaceable>.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:242
+#: best-pkging-practices.dbk:241
#, no-wrap
msgid ""
+"\n"
"<replaceable>package-name</replaceable> are "
-"<replaceable>synopsis</replaceable>."
+"<replaceable>synopsis</replaceable>.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:282
+#: best-pkging-practices.dbk:281
#, no-wrap
-msgid "ispell -d american -g debian/control"
+msgid ""
+"\n"
+"ispell -d american -g debian/control\n"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:285
+#: best-pkging-practices.dbk:284
#, no-wrap
-msgid "aspell -d en -D -c debian/control"
+msgid ""
+"\n"
+"aspell -d en -D -c debian/control\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
#: best-pkging-practices.dbk:312
msgid ""
-"If the package is experimental, or there are other reasons it should not be "
-"used, if there are other packages that should be used instead, it should be "
-"here as well."
+"If the package is <literal>experimental</literal>, or there are other "
+"reasons it should not be used, if there are other packages that should be "
+"used instead, it should be here as well."
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
# type: Content of: <chapter><section><section><para>
#: best-pkging-practices.dbk:334
msgid ""
-"We recommend that you add the URL for the package's home page to the package "
-"description in <filename>debian/control</filename>. This information should "
-"be added at the end of description, using the following format:"
-msgstr ""
-
-# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:339
-#, no-wrap
-msgid ""
-".\n"
-" Homepage: http://some-project.some-place.org/"
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:343
-msgid ""
-"Note the spaces prepending the line, which serves to break the lines "
-"correctly. To see an example of how this displays, see <ulink "
-"url=\"&url-eg-desc-upstream-info;\"></ulink>."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:348
-msgid ""
-"If there is no home page for the software, this should naturally be left "
-"out."
-msgstr ""
-
-# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:351
-msgid ""
-"Note that we expect this field will eventually be replaced by a proper "
-"<filename>debian/control</filename> field understood by "
-"<command>dpkg</command> and <literal>&packages-host;</literal>. If you "
-"don't want to bother migrating the home page from the description to this "
-"field, you should probably wait until that is available. Please make sure "
-"that this line matches the regular expression <literal>/^ Homepage: [^ "
-"]*$/</literal>, as this allows <filename>&packages-host;</filename> to parse "
-"it correctly."
+"We recommend that you add the URL for the package's home page in the "
+"<literal>Homepage</literal> field of the <literal>Source</literal> section "
+"in <filename>debian/control</filename>. Adding this information in the "
+"package description itself is considered deprecated."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:362
+#: best-pkging-practices.dbk:342
msgid "Version Control System location"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:364
+#: best-pkging-practices.dbk:344
msgid ""
"There are additional fields for the location of the Version Control System "
"in <filename>debian/control</filename>."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:368
-msgid "XS-Vcs-Browser"
+#: best-pkging-practices.dbk:348
+msgid "Vcs-Browser"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:370
+#: best-pkging-practices.dbk:350
msgid ""
"Value of this field should be a <literal>http://</literal> URL pointing to a "
"web-browsable copy of the Version Control System repository used to maintain "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:375
+#: best-pkging-practices.dbk:355
msgid ""
"The information is meant to be useful for the final user, willing to browse "
"the latest work done on the package (e.g. when looking for the patch fixing "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:382
-msgid "XS-Vcs-*"
+#: best-pkging-practices.dbk:362
+msgid "Vcs-*"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:384
+#: best-pkging-practices.dbk:364
msgid ""
"Value of this field should be a string identifying unequivocally the "
"location of the Version Control System repository used to maintain the given "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:395
+#: best-pkging-practices.dbk:375
msgid ""
"The information is meant to be useful for a user knowledgeable in the given "
"Version Control System and willing to build the current version of a package "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:406
+#: best-pkging-practices.dbk:386
msgid ""
"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>XS-Vcs-Browser</literal> field described above is also shown."
+"<literal>Vcs-Browser</literal> and <literal>Homepage</literal> fields "
+"described above is also shown."
msgstr ""
# type: Content of: <chapter><section><section><section><screen>
-#: best-pkging-practices.dbk:414
+#: best-pkging-practices.dbk:394
#, no-wrap
msgid ""
-"Source: vim\n"
+"\n"
+" Source: vim\n"
" Section: editors\n"
" Priority: optional\n"
" <snip>\n"
-" XS-Vcs-Svn: svn://svn.debian.org/svn/pkg-vim/trunk/packages/vim\n"
-" XS-Vcs-Browser: http://svn.debian.org/wsvn/pkg-vim/trunk/packages/vim"
+" Vcs-Svn: svn://svn.debian.org/svn/pkg-vim/trunk/packages/vim\n"
+" Vcs-Browser: http://svn.debian.org/wsvn/pkg-vim/trunk/packages/vim\n"
+" Homepage: http://www.vim.org\n"
msgstr ""
# type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:428
+#: best-pkging-practices.dbk:410
msgid "Best practices for <filename>debian/changelog</filename>"
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:430
+#: best-pkging-practices.dbk:412
msgid ""
"The following practices supplement the <ulink "
"url=\"&url-debian-policy;ch-docs.html#s-changelogs\">Policy on changelog "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:435
+#: best-pkging-practices.dbk:417
msgid "Writing useful changelog entries"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:437
+#: best-pkging-practices.dbk:419
msgid ""
"The changelog entry for a package revision documents changes in that "
"revision, and only them. Concentrate on describing significant and "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:442
+#: best-pkging-practices.dbk:424
msgid ""
"Focus on <emphasis>what</emphasis> was changed — who, how and when are "
"usually less important. Having said that, remember to politely attribute "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:448
+#: best-pkging-practices.dbk:430
msgid ""
"There's no need to elaborate the trivial and obvious changes. You can also "
"aggregate several changes in one entry. On the other hand, don't be overly "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:455
+#: best-pkging-practices.dbk:437
msgid ""
"Use common English so that the majority of readers can comprehend it. Avoid "
"abbreviations, tech-speak and jargon when explaining changes that close "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:461
+#: best-pkging-practices.dbk:443
msgid ""
"It is sometimes desirable to prefix changelog entries with the names of the "
"files that were changed. However, there's no need to explicitly list each "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:467
+#: best-pkging-practices.dbk:449
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 "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:474
+#: best-pkging-practices.dbk:456
msgid "Common misconceptions about changelog entries"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:476
+#: best-pkging-practices.dbk:458
msgid ""
"The changelog entries should <emphasis role=\"strong\">not</emphasis> "
"document generic packaging issues (Hey, if you're looking for foo.conf, it's "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:484
+#: best-pkging-practices.dbk:466
msgid ""
"The only bugs closed with a changelog entry should be those that are "
"actually fixed in the same package revision. Closing unrelated bugs in the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:489
+#: best-pkging-practices.dbk:471
msgid ""
"The changelog entries should <emphasis role=\"strong\">not</emphasis> be "
"used for random discussion with bug reporters (I don't see segfaults when "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:500
+#: best-pkging-practices.dbk:482
msgid ""
"It is an old tradition to acknowledge bugs fixed in non-maintainer uploads "
"in the first changelog entry of the proper maintainer upload. As we have "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:508
+#: best-pkging-practices.dbk:490
msgid "Common errors in changelog entries"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:510
+#: best-pkging-practices.dbk:492
msgid ""
"The following examples demonstrate some common errors or examples of bad "
"style in changelog entries."
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:514
+#: best-pkging-practices.dbk:495
#, no-wrap
-msgid "* Fixed all outstanding bugs."
+msgid ""
+"\n"
+" * Fixed all outstanding bugs.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:517
+#: best-pkging-practices.dbk:499
msgid "This doesn't tell readers anything too useful, obviously."
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:520
+#: best-pkging-practices.dbk:501
#, no-wrap
-msgid "* Applied patch from Jane Random."
+msgid ""
+"\n"
+" * Applied patch from Jane Random.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:523
+#: best-pkging-practices.dbk:505
msgid "What was the patch about?"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:526
+#: best-pkging-practices.dbk:507
#, no-wrap
-msgid "* Late night install target overhaul."
+msgid ""
+"\n"
+" * Late night install target overhaul.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:529
+#: best-pkging-practices.dbk:511
msgid ""
"Overhaul which accomplished what? Is the mention of late night supposed to "
"remind us that we shouldn't trust that code?"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:533
+#: best-pkging-practices.dbk:514
#, no-wrap
-msgid "* Fix vsync FU w/ ancient CRTs."
+msgid ""
+"\n"
+" * Fix vsync FU w/ ancient CRTs.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:536
+#: best-pkging-practices.dbk:518
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>
-#: best-pkging-practices.dbk:540
+#: best-pkging-practices.dbk:521
#, no-wrap
-msgid "* This is not a bug, closes: #nnnnnn."
+msgid ""
+"\n"
+" * This is not a bug, closes: #nnnnnn.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:543
+#: best-pkging-practices.dbk:525
msgid ""
"First of all, there's absolutely no need to upload the package to convey "
"this information; instead, use the bug tracking system. Secondly, there's "
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:548
+#: best-pkging-practices.dbk:529
#, no-wrap
-msgid "* Has been fixed for ages, but I forgot to close; closes: #54321."
+msgid ""
+"\n"
+" * Has been fixed for ages, but I forgot to close; closes: #54321.\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:551
+#: best-pkging-practices.dbk:533
msgid ""
"If for some reason you didn't mention the bug number in a previous changelog "
"entry, there's no problem, just close the bug normally in the BTS. There's "
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:558
+#: best-pkging-practices.dbk:539
#, no-wrap
-msgid "* Closes: #12345, #12346, #15432"
+msgid ""
+"\n"
+" * Closes: #12345, #12346, #15432\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:561
+#: best-pkging-practices.dbk:543
msgid ""
"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:567
+#: best-pkging-practices.dbk:549
msgid "Supplementing changelogs with NEWS.Debian files"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:569
+#: best-pkging-practices.dbk:551
msgid ""
-"Important news about changes in a package can also be put in NEWS.Debian "
-"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 NEWS.Debian file after the install. And it's better than listing "
-"major changes in README.Debian, 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 "
+"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."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:578
+#: best-pkging-practices.dbk:562
msgid ""
"The file format is the same as a debian changelog file, but leave off the "
"asterisks and describe each news item with a full paragraph when necessary "
"rather than the more concise summaries that would go in a changelog. It's a "
-"good idea to run your file through dpkg-parsechangelog to check its "
-"formatting as it will not be automatically checked during build as the "
-"changelog is. Here is an example of a real NEWS.Debian file:"
+"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:"
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:586
+#: best-pkging-practices.dbk:570
#, no-wrap
msgid ""
+"\n"
"cron (3.0pl1-74) unstable; urgency=low\n"
"\n"
" The checksecurity script is no longer included with the cron package:\n"
" package.\n"
"\n"
" -- Steve Greenland <stevegr@debian.org> Sat, 6 Sep 2003 17:15:03 "
-"-0500"
+"-0500\n"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:596
+#: best-pkging-practices.dbk:581
msgid ""
-"The NEWS.Debian file is installed as "
-"/usr/share/doc/<package>/NEWS.Debian.gz. It is compressed, and always "
-"has that name even in Debian native packages. If you use debhelper, "
-"dh_installchangelogs will install debian/NEWS 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:602
+#: best-pkging-practices.dbk:588
msgid ""
-"Unlike changelog files, you need not update NEWS.Debian files with every "
-"release. Only update them if you have something particularly newsworthy "
-"that user should know about. If you have no news at all, there's no need to "
-"ship a NEWS.Debian file in your package. No news is good news!"
+"Unlike changelog files, you need not update <filename>NEWS.Debian</filename> "
+"files with every release. Only update them if you have something "
+"particularly newsworthy that user should know about. If you have no news at "
+"all, there's no need to ship a <filename>NEWS.Debian</filename> file in your "
+"package. No news is good news!"
msgstr ""
# type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:623
+#: best-pkging-practices.dbk:610
msgid "Best practices for maintainer scripts"
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:625
+#: best-pkging-practices.dbk:612
msgid ""
"Maintainer scripts include the files <filename>debian/postinst</filename>, "
"<filename>debian/preinst</filename>, <filename>debian/prerm</filename> and "
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:633
+#: best-pkging-practices.dbk:620
msgid ""
"Maintainer scripts must be idempotent. That means that you need to make "
"sure nothing bad will happen if the script is called twice where it would "
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:638
+#: best-pkging-practices.dbk:625
msgid ""
"Standard input and output may be redirected (e.g. into pipes) for logging "
"purposes, so don't rely on them being a tty."
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:642
+#: best-pkging-practices.dbk:629
msgid ""
"All prompting or interactive configuration should be kept to a minimum. "
"When it is necessary, you should use the <systemitem "
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:649
+#: best-pkging-practices.dbk:636
msgid ""
"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 "
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:656
+#: best-pkging-practices.dbk:643
msgid ""
"If you change your maintainer scripts, be sure to test package removal, "
"double installation, and purging. Be sure that a purged package is "
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:662
+#: best-pkging-practices.dbk:649
msgid ""
"If you need to check for the existence of a command, you should use "
"something like"
msgstr ""
# type: Content of: <chapter><section><programlisting>
-#: best-pkging-practices.dbk:665
+#: best-pkging-practices.dbk:652
#, no-wrap
msgid "if [ -x /usr/sbin/install-docs ]; then ..."
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:667
+#: best-pkging-practices.dbk:654
msgid ""
"If you don't wish to hard-code the path of a command in your maintainer "
"script, the following POSIX-compliant shell function may help:"
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:672
+#: best-pkging-practices.dbk:659
msgid ""
"You can use this function to search <literal>$PATH</literal> for a command "
"name, passed as an argument. It returns true (zero) if the command was "
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:679
+#: best-pkging-practices.dbk:666
msgid ""
"While <command>which</command> is an acceptable alternative, since it is "
"from the required <systemitem role=\"package\">debianutils</systemitem> "
msgstr ""
# type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:689
+#: best-pkging-practices.dbk:676
msgid ""
"Configuration management with <systemitem "
"role=\"package\">debconf</systemitem>"
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:691
+#: best-pkging-practices.dbk:678
msgid ""
"<systemitem role=\"package\">Debconf</systemitem> is a configuration "
"management system which can be used by all the various packaging scripts "
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:699
+#: best-pkging-practices.dbk:686
msgid ""
"Debconf is a great tool but it is often poorly used. Many common mistakes "
"are listed in the <citerefentry> "
msgstr ""
# type: Content of: <chapter><section><para>
-#: best-pkging-practices.dbk:706
+#: best-pkging-practices.dbk:693
msgid ""
"These guidelines include some writing style and typography recommendations, "
"general considerations about debconf usage as well as more specific "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:712
+#: best-pkging-practices.dbk:699
msgid "Do not abuse debconf"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:714
+#: best-pkging-practices.dbk:701
msgid ""
"Since debconf appeared in Debian, it has been widely abused and several "
"criticisms received by the Debian distribution come from debconf abuse with "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:720
+#: best-pkging-practices.dbk:707
msgid ""
"Keep usage notes to what they belong: the NEWS.Debian, or README.Debian "
"file. Only use notes for important notes which may directly affect the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:726
+#: best-pkging-practices.dbk:713
msgid ""
"Carefully choose the questions priorities in maintainer scripts. See "
"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:734
+#: best-pkging-practices.dbk:721
msgid "General recommendations for authors and translators"
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:736
+#: best-pkging-practices.dbk:723
msgid "Write correct English"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:738
+#: best-pkging-practices.dbk:725
msgid ""
"Most Debian package maintainers are not native English speakers. So, "
"writing properly phrased templates may not be easy for them."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:742
+#: best-pkging-practices.dbk:729
msgid ""
"Please use (and abuse) &email-debian-l10n-english; mailing list. Have your "
"templates proofread."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:746
+#: best-pkging-practices.dbk:733
msgid ""
"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>
-#: best-pkging-practices.dbk:750
+#: best-pkging-practices.dbk:737
msgid ""
"Avoid technical jargon as much as possible. If some terms sound common to "
"you, they may be impossible to understand for others. If you cannot avoid "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:758
+#: best-pkging-practices.dbk:745
msgid "Be kind to translators"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:760
+#: best-pkging-practices.dbk:747
msgid ""
"Debconf templates may be translated. Debconf, along with its sister package "
"<command>po-debconf</command> offers a simple framework for getting "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:765
+#: best-pkging-practices.dbk:752
msgid ""
"Please use gettext-based templates. Install <systemitem "
"role=\"package\">po-debconf</systemitem> on your development system and read "
-"its documentation (man po-debconf is a good start)."
+"its documentation (<literal>man po-debconf</literal> is a good start)."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:770
+#: best-pkging-practices.dbk:757
msgid ""
"Avoid changing templates too often. Changing templates text induces more "
"work to translators which will get their translation fuzzied. If you plan "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:779
+#: best-pkging-practices.dbk:766
msgid ""
-"The use of the <command>podebconf-report-po</command> from the po-debconf "
-"package is highly recommended to warn translators which have incomplete "
-"translations and request them for updates."
+"The use of the <command>podebconf-report-po</command> from the <systemitem "
+"role=\"package\">po-debconf</systemitem> package is highly recommended to "
+"warn translators which have incomplete translations and request them for "
+"updates."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:784
+#: best-pkging-practices.dbk:771
msgid ""
"If in doubt, you may also contact the translation team for a given language "
"(debian-l10n-xxxxx@&lists-host;), or the &email-debian-i18n; mailing list."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:789
+#: best-pkging-practices.dbk:776
msgid ""
"Calls for translations posted to &email-debian-i18n; with the "
"<filename>debian/po/templates.pot</filename> file attached or referenced in "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:798
+#: best-pkging-practices.dbk:785
msgid "Unfuzzy complete translations when correcting typos and spelling"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:800
+#: best-pkging-practices.dbk:787
msgid ""
"When the text of a debconf template is corrected and you are <emphasis "
"role=\"strong\">sure</emphasis> that the change does <emphasis "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:806
+#: best-pkging-practices.dbk:793
msgid ""
"If you don't do so, the whole template will not be translated as long as a "
"translator will send you an update."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:810
+#: best-pkging-practices.dbk:797
msgid ""
-"To <emphasis role=\"strong\">unfuzzy</emphasis> translations, you can "
-"proceed the following way:"
+"To <literal>unfuzzy</literal> translations, you can proceed the following "
+"way:"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:816
+#: best-pkging-practices.dbk:803
msgid ""
"Put all incomplete PO files out of the way. You can check the completeness "
"by using (needs the <systemitem role=\"package\">gettext</systemitem> "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:820
+#: best-pkging-practices.dbk:807
#, no-wrap
msgid ""
"for i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null\n"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:825
+#: best-pkging-practices.dbk:812
msgid ""
"move all files which report either fuzzy strings to a temporary place. "
"Files which report no fuzzy strings (only translated and untranslated) will "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:832
+#: best-pkging-practices.dbk:819
msgid ""
"now <emphasis role=\"strong\">and now only</emphasis>, modify the template "
"for the typos and check again that translation are not impacted (typos, "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:839
+#: best-pkging-practices.dbk:826
msgid ""
"run <command>debconf-updatepo</command>. This will fuzzy all strings you "
"modified in translations. You can see this by running the above again"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:845
+#: best-pkging-practices.dbk:832
msgid "use the following command:"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting>
-#: best-pkging-practices.dbk:847
+#: best-pkging-practices.dbk:834
#, no-wrap
msgid "for i in debian/po/*po; do msgattrib --output-file=$i --clear-fuzzy $i; done"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:851
+#: best-pkging-practices.dbk:838
msgid ""
"move back to debian/po the files which showed fuzzy strings in the first "
"step"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:856
+#: best-pkging-practices.dbk:843
msgid "run <command>debconf-updatepo</command> again"
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:863
+#: best-pkging-practices.dbk:850
msgid "Do not make assumptions about interfaces"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:865
+#: best-pkging-practices.dbk:852
msgid ""
"Templates text should not make reference to widgets belonging to some "
"debconf interfaces. Sentences like If you answer Yes... have no meaning "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:870
+#: best-pkging-practices.dbk:857
msgid ""
"String templates should also avoid mentioning the default values in their "
"description. First, because this is redundant with the values seen by the "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:876
+#: best-pkging-practices.dbk:863
msgid ""
"More generally speaking, try to avoid referring to user actions. Just give "
"facts."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:882
+#: best-pkging-practices.dbk:869
msgid "Do not use first person"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:884
+#: best-pkging-practices.dbk:871
msgid ""
"You should avoid the use of first person (I will do this... or We "
"recommend...). The computer is not a person and the Debconf templates do "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:894
+#: best-pkging-practices.dbk:881
msgid "Be gender neutral"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:896
+#: best-pkging-practices.dbk:883
msgid ""
"The world is made of men and women. Please use gender-neutral constructions "
"in your writing."
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:904
+#: best-pkging-practices.dbk:891
msgid "Templates fields definition"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:906
+#: best-pkging-practices.dbk:893
msgid ""
"This part gives some information which is mostly taken from the "
"<citerefentry> <refentrytitle>debconf-devel</refentrytitle> "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:911
+#: best-pkging-practices.dbk:898
msgid "Type"
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:913
+#: best-pkging-practices.dbk:900
msgid "string:"
msgstr ""
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:915
+#: best-pkging-practices.dbk:902
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:920
+#: best-pkging-practices.dbk:907
msgid "password:"
msgstr ""
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:922
+#: best-pkging-practices.dbk:909
msgid ""
"Prompts the user for a password. Use this with caution; be aware that the "
"password the user enters will be written to debconf's database. You should "
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:929
+#: best-pkging-practices.dbk:916
msgid "boolean:"
msgstr ""
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:931
+#: best-pkging-practices.dbk:918
msgid ""
"A true/false choice. Remember: true/false, <emphasis role=\"strong\">not "
"yes/no</emphasis>..."
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:937
+#: best-pkging-practices.dbk:924
msgid "select:"
msgstr ""
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:939
+#: best-pkging-practices.dbk:926
msgid ""
"A choice between one of a number of values. The choices must be specified "
"in a field named 'Choices'. Separate the possible values with commas and "
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:946
+#: best-pkging-practices.dbk:933
msgid "multiselect:"
msgstr ""
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:948
+#: best-pkging-practices.dbk:935
msgid ""
"Like the select data type, except the user can choose any number of items "
"from the choices list (or chose none of them)."
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:954
+#: best-pkging-practices.dbk:941
msgid "note:"
msgstr ""
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:956
+#: best-pkging-practices.dbk:943
msgid ""
"Rather than being a question per se, this datatype indicates a note that can "
"be displayed to the user. It should be used only for important notes that "
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:965
+#: best-pkging-practices.dbk:952
msgid "text:"
msgstr ""
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:967
+#: best-pkging-practices.dbk:954
msgid "This type is now considered obsolete: don't use it."
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:972
+#: best-pkging-practices.dbk:959
msgid "error:"
msgstr ""
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:974
+#: best-pkging-practices.dbk:961
msgid ""
"This type is designed to handle error messages. It is mostly similar to the "
"note type. Frontends may present it differently (for instance, the dialog "
msgstr ""
# type: Content of: <chapter><section><section><section><section><para>
-#: best-pkging-practices.dbk:979
+#: best-pkging-practices.dbk:966
msgid ""
"It is recommended to use this type for any message that needs user attention "
"for a correction of any kind."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:987
+#: best-pkging-practices.dbk:974
msgid "Description: short and extended description"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:989
+#: best-pkging-practices.dbk:976
msgid ""
"Template descriptions have two parts: short and extended. The short "
"description is in the Description: line of the template."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:993
+#: best-pkging-practices.dbk:980
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 "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:999
+#: best-pkging-practices.dbk:986
msgid ""
"The short description should be able to stand on its own. Some interfaces "
"do not show the long description by default, or only if the user explicitely "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1005
+#: best-pkging-practices.dbk:992
msgid ""
"The short description does not necessarily have to be a full sentence. This "
"is part of the keep it short and efficient recommendation."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1009
+#: best-pkging-practices.dbk:996
msgid ""
"The extended description should not repeat the short description word for "
"word. If you can't think up a long description, then first, think some "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1016
+#: best-pkging-practices.dbk:1003
msgid ""
"The extended description should use complete sentences. Paragraphs should "
"be kept short for improved readability. Do not mix two ideas in the same "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1021
+#: best-pkging-practices.dbk:1008
msgid ""
"Don't be too verbose. User tend to ignore too long screens. 20 lines are "
"by experience a border you shouldn't cross, because that means that in the "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1027
+#: best-pkging-practices.dbk:1014
msgid ""
"The extended description should <emphasis role=\"strong\">never</emphasis> "
"include a question."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1031
+#: best-pkging-practices.dbk:1018
msgid ""
"For specific rules depending on templates type (string, boolean, etc.), "
"please read below."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1037
+#: best-pkging-practices.dbk:1024
msgid "Choices"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1039
+#: best-pkging-practices.dbk:1026
msgid ""
"This field should be used for Select and Multiselect types. It contains the "
"possible choices which will be presented to users. These choices should be "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1046
+#: best-pkging-practices.dbk:1033
msgid "Default"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1048
+#: best-pkging-practices.dbk:1035
msgid ""
"This field is optional. It contains the default answer for string, select "
"and multiselect templates. For multiselect templates, it may contain a "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1057
+#: best-pkging-practices.dbk:1044
msgid "Templates fields specific style guide"
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1059
+#: best-pkging-practices.dbk:1046
msgid "Type field"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1061
+#: best-pkging-practices.dbk:1048
msgid ""
"No specific indication except: use the appropriate type by referring to the "
"previous section."
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1067
+#: best-pkging-practices.dbk:1054
msgid "Description field"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1069
+#: best-pkging-practices.dbk:1056
msgid ""
"Below are specific instructions for properly writing the Description (short "
"and extended) depending on the template type."
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1073
+#: best-pkging-practices.dbk:1060
msgid "String/password templates"
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1077
+#: best-pkging-practices.dbk:1064
msgid ""
"The short description is a prompt and <emphasis "
"role=\"strong\">not</emphasis> a title. Avoid question style prompts (IP "
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1084
+#: best-pkging-practices.dbk:1071
msgid ""
"The extended description is a complement to the short description. In the "
"extended part, explain what is being asked, rather than ask the same "
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1094
+#: best-pkging-practices.dbk:1081
msgid "Boolean templates"
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1098
+#: best-pkging-practices.dbk:1085
msgid ""
"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 "
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1106
+#: best-pkging-practices.dbk:1093
msgid ""
"Again, please avoid referring to specific interface widgets. A common "
"mistake for such templates is if you answer Yes-type constructions."
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1114
+#: best-pkging-practices.dbk:1101
msgid "Select/Multiselect"
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1118
+#: best-pkging-practices.dbk:1105
msgid ""
"The short description is a prompt and <emphasis "
"role=\"strong\">not</emphasis> a title. Do <emphasis "
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1126
+#: best-pkging-practices.dbk:1113
msgid ""
"The extended description will complete the short description. It may refer "
"to the available choices. It may also mention that the user may choose more "
msgstr ""
# type: Content of: <chapter><section><section><section><section><title>
-#: best-pkging-practices.dbk:1136
+#: best-pkging-practices.dbk:1123
msgid "Notes"
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1140
+#: best-pkging-practices.dbk:1127
msgid "The short description should be considered to be a *title*."
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1145
+#: best-pkging-practices.dbk:1132
msgid ""
"The extended description is what will be displayed as a more detailed "
"explanation of the note. Phrases, no terse writing style."
msgstr ""
# type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1151
+#: best-pkging-practices.dbk:1138
msgid ""
"<emphasis role=\"strong\">Do not abuse debconf.</emphasis> Notes are the "
"most common way to abuse debconf. As written in debconf-devel manual page: "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1166
+#: best-pkging-practices.dbk:1153
msgid "Choices field"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1168
+#: best-pkging-practices.dbk:1155
msgid ""
"If the Choices are likely to change often, please consider using the "
"__Choices trick. This will split each individual choice into a single "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1175 best-pkging-practices.dbk:1213
+#: best-pkging-practices.dbk:1162 best-pkging-practices.dbk:1200
msgid "Default field"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1177
+#: best-pkging-practices.dbk:1164
msgid ""
"If the default value, for a select template, is likely to vary depending on "
"the user language (for instance, if the choice is a language choice), please "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1182
+#: best-pkging-practices.dbk:1169
msgid ""
"This special field allow translators to put the most appropriate choice "
"according to their own language. It will become the default choice when "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1188
+#: best-pkging-practices.dbk:1175
msgid "Example, taken from the geneweb package templates:"
msgstr ""
# type: Content of: <chapter><section><section><section><screen>
-#: best-pkging-practices.dbk:1191
+#: best-pkging-practices.dbk:1177
#, no-wrap
msgid ""
+"\n"
"Template: geneweb/lang\n"
"Type: select\n"
"__Choices: Afrikaans (af), Bulgarian (bg), Catalan (ca), Chinese (zh), Czech "
"# WARNING : you MUST use the ENGLISH FORM of your language\n"
"# For instance, the french translator will need to put French (fr) here.\n"
"_DefaultChoice: English (en)[ translators, please see comment in PO files]\n"
-"_Description: Geneweb default language:"
+"_Description: Geneweb default language:\n"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1202
+#: best-pkging-practices.dbk:1189
msgid ""
"Note the use of brackets which allow internal comments in debconf fields. "
"Also note the use of comments which will show up in files the translators "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1207
+#: best-pkging-practices.dbk:1194
msgid ""
"The comments are needed as the DefaultChoice trick is a bit confusing: the "
"translators may put their own choice"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1215
+#: best-pkging-practices.dbk:1202
msgid ""
"Do NOT use empty default field. If you don't want to use default values, do "
"not use Default at all."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1219
+#: best-pkging-practices.dbk:1206
msgid ""
"If you use po-debconf (and you <emphasis role=\"strong\">should</emphasis>, "
"see 2.2), consider making this field translatable, if you think it may be "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1224
+#: best-pkging-practices.dbk:1211
msgid ""
"If the default value may vary depending on language/country (for instance "
"the default value for a language choice), consider using the special "
msgstr ""
# type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:1236
+#: best-pkging-practices.dbk:1223
msgid "Internationalization"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1238
+#: best-pkging-practices.dbk:1225
msgid "Handling debconf translations"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1240
+#: best-pkging-practices.dbk:1227
msgid ""
"Like porters, translators have a difficult task. They work on many packages "
"and must collaborate with many different maintainers. Moreover, most of the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1246
+#: best-pkging-practices.dbk:1233
msgid ""
"The goal of <systemitem role=\"package\">debconf</systemitem> was to make "
"packages configuration easier for maintainers and for users. Originally, "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1256
+#: best-pkging-practices.dbk:1243
msgid ""
"Using <systemitem role=\"package\">po-debconf</systemitem>, the translation "
"is stored in <filename>po</filename> files (drawing from "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1272
+#: best-pkging-practices.dbk:1259
msgid "Internationalized documentation"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1274
+#: best-pkging-practices.dbk:1261
msgid ""
"Internationalizing documentation is crucial for users, but a lot of labor. "
"There's no way to eliminate all that work, but you can make things easier "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1279
+#: best-pkging-practices.dbk:1266
msgid ""
"If you maintain documentation of any size, its easier for translators if "
"they have access to a source control system. That lets translators see the "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1293
+#: best-pkging-practices.dbk:1280
msgid ""
"If you maintain XML or SGML documentation, we suggest that you isolate any "
"language-independent information and define those as entities in a separate "
msgstr ""
# type: Content of: <chapter><section><title>
-#: best-pkging-practices.dbk:1303
+#: best-pkging-practices.dbk:1290
msgid "Common packaging situations"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1314
+#: best-pkging-practices.dbk:1301
msgid "Packages using <command>autoconf</command>/<command>automake</command>"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1316
+#: best-pkging-practices.dbk:1303
msgid ""
"Keeping <command>autoconf</command>'s <filename>config.sub</filename> and "
"<filename>config.guess</filename> files up to date is critical for porters, "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1328
+#: best-pkging-practices.dbk:1315
msgid "Libraries"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1330
+#: best-pkging-practices.dbk:1317
msgid ""
"Libraries are always difficult to package for various reasons. The policy "
"imposes many constraints to ease their maintenance and to make sure upgrades "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1336
+#: best-pkging-practices.dbk:1323
msgid ""
"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>
-#: best-pkging-practices.dbk:1343
+#: best-pkging-practices.dbk:1330
msgid "Documentation"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1345
+#: best-pkging-practices.dbk:1332
msgid ""
"Be sure to follow the <ulink url=\"&url-debian-policy;ch-docs.html\">Policy "
"on documentation</ulink>."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1350
+#: best-pkging-practices.dbk:1337
msgid ""
"If your package contains documentation built from XML or SGML, we recommend "
"you not ship the XML or SGML source in the binary package(s). If users want "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1355
+#: best-pkging-practices.dbk:1342
msgid ""
"Policy specifies that documentation should be shipped in HTML format. We "
"also recommend shipping documentation in PDF and plain text format if "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1362
+#: best-pkging-practices.dbk:1349
msgid ""
"Major shipped manuals should register themselves with <systemitem "
"role=\"package\">doc-base</systemitem> on installation. See the <systemitem "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1370
+#: best-pkging-practices.dbk:1357
msgid "Specific types of packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1372
+#: best-pkging-practices.dbk:1359
msgid ""
"Several specific types of packages have special sub-policies and "
"corresponding packaging rules and practices:"
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1378
+#: best-pkging-practices.dbk:1365
msgid ""
"Perl related packages have a <ulink url=\"&url-perl-policy;\">Perl "
"policy</ulink>, some examples of packages following that policy are "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1387
+#: best-pkging-practices.dbk:1374
msgid ""
"Python related packages have their python policy; see &file-python-policy; "
"in the <systemitem role=\"package\">python</systemitem> package."
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1394
+#: best-pkging-practices.dbk:1381
msgid ""
"Emacs related packages have the <ulink url=\"&url-emacs-policy;\">emacs "
"policy</ulink>."
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1401
+#: best-pkging-practices.dbk:1388
msgid ""
"Java related packages have their <ulink url=\"&url-java-policy;\">java "
"policy</ulink>."
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1408
+#: best-pkging-practices.dbk:1395
msgid ""
"Ocaml related packages have their own policy, found in &file-ocaml-policy; "
"from the <systemitem role=\"package\">ocaml</systemitem> package. A good "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1416
+#: best-pkging-practices.dbk:1403
msgid ""
"Packages providing XML or SGML DTDs should conform to the recommendations "
"found in the <systemitem role=\"package\">sgml-base-doc</systemitem> "
msgstr ""
# type: Content of: <chapter><section><section><itemizedlist><listitem><para>
-#: best-pkging-practices.dbk:1422
+#: best-pkging-practices.dbk:1409
msgid ""
"Lisp packages should register themselves with <systemitem "
"role=\"package\">common-lisp-controller</systemitem>, about which see "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1452
+#: best-pkging-practices.dbk:1439
msgid "Architecture-independent data"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1454
+#: best-pkging-practices.dbk:1441
msgid ""
"It is not uncommon to have a large amount of architecture-independent data "
"packaged with a program. For example, audio files, a collection of icons, "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1461
+#: best-pkging-practices.dbk:1448
msgid ""
"However, if the size of the data is considerable, consider splitting it out "
"into a separate, architecture-independent package (_all.deb). By doing "
".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> or <command>linda</command> "
-"(see <xref linkend=\"tools-lint\"/> ) when run over the entire Debian "
-"archive."
+"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><title>
-#: best-pkging-practices.dbk:1473
+#: best-pkging-practices.dbk:1460
msgid "Needing a certain locale during build"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1475
+#: best-pkging-practices.dbk:1462
msgid ""
"If you need a certain locale during build, you can create a temporary file "
"via this trick:"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1479
+#: best-pkging-practices.dbk:1466
msgid ""
"If you set <varname>LOCPATH</varname> to the equivalent of "
"<filename>/usr/lib/locale</filename>, and <varname>LC_ALL</varname> to the "
msgstr ""
# type: Content of: <chapter><section><section><screen>
-#: best-pkging-practices.dbk:1484
+#: best-pkging-practices.dbk:1470
#, no-wrap
msgid ""
+"\n"
"LOCALE_PATH=debian/tmpdir/usr/lib/locale\n"
"LOCALE_NAME=en_IN\n"
"LOCALE_CHARSET=UTF-8\n"
"$LOCALE_PATH/$LOCALE_NAME.$LOCALE_CHARSET\n"
"\n"
"# Using the locale\n"
-"LOCPATH=$LOCALE_PATH LC_ALL=$LOCALE_NAME.$LOCALE_CHARSET date"
+"LOCPATH=$LOCALE_PATH LC_ALL=$LOCALE_NAME.$LOCALE_CHARSET date\n"
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1497
+#: best-pkging-practices.dbk:1484
msgid "Make transition packages deborphan compliant"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1499
+#: best-pkging-practices.dbk:1486
msgid ""
"Deborphan is a program for helping users to detect which packages can safely "
"be removed from the system, i.e. the ones that have no packages depending "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1506
+#: best-pkging-practices.dbk:1493
msgid ""
-"For example, with --guess-dummy, deborphan 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>
-#: best-pkging-practices.dbk:1512
+#: best-pkging-practices.dbk:1500
msgid ""
"So, when you are creating such a package, please make sure to add this text "
"to your short description. If you are looking for examples, just run: "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1520
+#: best-pkging-practices.dbk:1508
msgid "Best practices for <filename>orig.tar.gz</filename> files"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1522
+#: best-pkging-practices.dbk:1510
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:1526
+#: best-pkging-practices.dbk:1514
msgid "Pristine source"
msgstr ""
# type: Content of: <chapter><section><section><section><para><footnote>
-#: best-pkging-practices.dbk:1528
+#: best-pkging-practices.dbk:1516
msgid ""
"The defining characteristic of a pristine source tarball is that the "
-".orig.tar.gz file is byte-for-byte identical to a tarball officially "
-"distributed by the upstream author. <footnote>"
+"<literal>.orig.tar.gz</literal> file is byte-for-byte identical to a tarball "
+"officially distributed by the upstream author. <footnote>"
msgstr ""
# type: Content of: <chapter><section><section><section><para><footnote><para>
-#: best-pkging-practices.dbk:1530
+#: best-pkging-practices.dbk:1518
msgid ""
"We cannot prevent upstream authors from changing the tarball they distribute "
"without also incrementing the version number, so there can be no guarantee "
"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 comression in his original "
-"distribution and then re-<literal>gzip</literal>s it), that's just too bad. "
-"Since there is no good way to upload a new .orig.tar.gz for the same "
-"version, there is not even any point in treating this situation as a bug."
+"distribution and then re-<command>gzip</command>s it), that's just too bad. "
+"Since there is no good way to upload a new <literal>.orig.tar.gz</literal> "
+"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:1540
+#: best-pkging-practices.dbk:1528
msgid ""
"</footnote> This makes it possible to use checksums to easily verify that "
"all changes between Debian's version and upstream's are contained in the "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1548
+#: best-pkging-practices.dbk:1536
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:1556
+#: best-pkging-practices.dbk:1544
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:1559
+#: best-pkging-practices.dbk:1546
#, no-wrap
msgid ""
+"\n"
"zcat path/to/<packagename>_<upstream-version>.orig.tar.gz | tar "
-"xf -"
+"xf -\n"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1564
+#: best-pkging-practices.dbk:1552
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:1573
+#: best-pkging-practices.dbk:1561
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:1584
+#: best-pkging-practices.dbk:1572
msgid "Repackaged upstream source"
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1586
+#: best-pkging-practices.dbk:1574
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:1593
-msgid ""
-"In these cases the developer must construct a suitable .orig.tar.gz 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 <literal>.diff.gz</literal> and still has a version number composed "
-"of <literal><upstream-version></literal> and "
+#: best-pkging-practices.dbk:1581
+msgid ""
+"In these cases the developer must construct a suitable <literal>.orig.tar.gz "
+"</literal> 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 <literal>.diff.gz</literal> and still has a version "
+"number composed of <literal><upstream-version></literal> and "
"<literal><debian-revision></literal>."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1602
+#: best-pkging-practices.dbk:1590
msgid ""
"There may be cases where it is desirable to repackage the source even though "
"upstream distributes a <literal>.tar.gz</literal> that could in principle be "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1611
-msgid "A repackaged .orig.tar.gz"
+#: best-pkging-practices.dbk:1599
+msgid "A repackaged <literal>.orig.tar.gz</literal>"
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1616
+#: best-pkging-practices.dbk:1604
msgid ""
"<emphasis role=\"strong\">must</emphasis> contain detailed information how "
"the repackaged source was obtained, and how this can be reproduced in the "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote>
-#: best-pkging-practices.dbk:1628
+#: best-pkging-practices.dbk:1616
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 "
#. or similarly named
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote><para>
-#: best-pkging-practices.dbk:1630
+#: best-pkging-practices.dbk:1618
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:1642
+#: best-pkging-practices.dbk:1625
+msgid "</footnote>"
+msgstr ""
+
+# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
+#: best-pkging-practices.dbk:1630
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:1651
+#: best-pkging-practices.dbk:1639
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:1658
+#: best-pkging-practices.dbk:1646
msgid ""
"<emphasis role=\"strong\">should</emphasis> use "
"<literal><packagename>-<upstream-version>.orig</literal> as the "
msgstr ""
# type: Content of: <chapter><section><section><section><orderedlist><listitem><para>
-#: best-pkging-practices.dbk:1666
+#: best-pkging-practices.dbk:1654
msgid ""
"<emphasis role=\"strong\">should</emphasis> be gzipped with maximal "
"compression."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1671
+#: best-pkging-practices.dbk:1659
msgid ""
"The canonical way to meet the latter two points is to let "
"<literal>dpkg-source -b</literal> construct the repackaged tarball from an "
msgstr ""
# type: Content of: <chapter><section><section><section><title>
-#: best-pkging-practices.dbk:1677
+#: best-pkging-practices.dbk:1665
msgid "Changing binary files in <literal>diff.gz</literal>"
msgstr ""
# type: Content of: <chapter><section><section><section><para><footnote>
-#: best-pkging-practices.dbk:1679
+#: best-pkging-practices.dbk:1667
msgid ""
"Sometimes it is necessary to change binary files contained in the original "
"tarball, or to add binary files that are not in it. If this is done by "
msgstr ""
# type: Content of: <chapter><section><section><section><para><footnote><para>
-#: best-pkging-practices.dbk:1686
+#: best-pkging-practices.dbk:1674
msgid ""
"The file should have a name that makes it clear which binary file it "
"encodes. Usually, some postfix indicating the encoding should be appended "
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1694
+#: best-pkging-practices.dbk:1682
msgid ""
"&example-uu; </footnote>. The file would then be decoded and copied to its "
"place during the build process. Thus the change will be visible quite easy."
msgstr ""
# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1700
+#: best-pkging-practices.dbk:1688
msgid ""
"Some packages use <command>dbs</command> to manage patches to their upstream "
"source, and always create a new <literal>orig.tar.gz</literal> file that "
msgstr ""
# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1713
+#: best-pkging-practices.dbk:1701
msgid "Best practices for debug packages"
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1715
+#: best-pkging-practices.dbk:1703
msgid ""
"A debug package is a package with a name ending in -dbg, that contains "
"additional information that gdb can use. Since Debian binaries are stripped "
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1723
+#: best-pkging-practices.dbk:1711
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:1733
+#: best-pkging-practices.dbk:1721
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 "
"instead containing separated debugging symbols that gdb 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/path</filename>, where "
-"<emphasis>path</emphasis> is the path to the executable or library. For "
-"example, debugging symbols for <filename>/usr/bin/foo</filename> go in "
+"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>
-#: best-pkging-practices.dbk:1745
+#: best-pkging-practices.dbk:1733
msgid ""
-"The debugging symbols can be extracted from an object file using objcopy "
-"--only-keep-debug. Then the object file can be stripped, and objcopy "
-"--add-gnu-debuglink used to specify the path to the debugging symbol file. "
-"<citerefentry> <refentrytitle>objcopy</refentrytitle> "
-"<manvolnum>1</manvolnum> </citerefentry> explains in detail how this works."
+"The debugging symbols can be extracted from an object file using <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."
msgstr ""
# type: Content of: <chapter><section><section><para>
-#: best-pkging-practices.dbk:1752
+#: best-pkging-practices.dbk:1741
msgid ""
-"The dh_strip command in debhelper supports creating debug packages, and can "
-"take care of using objcopy to separate out the debugging symbols for you. "
-"If your package uses debhelper, all you need to do is call dh_strip "
-"--dbg-package=libfoo-dbg, and add an entry to debian/control for the debug "
-"package."
+"The <command>dh_strip</command> command in debhelper 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 debhelper, 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:1759
+#: best-pkging-practices.dbk:1748
msgid ""
"Note that the Debian 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:1763
+#: best-pkging-practices.dbk:1751
#, no-wrap
-msgid "Depends: libfoo-dbg (= ${binary:Version})"
+msgid ""
+"\n"
+"Depends: libfoo-dbg (= ${binary:Version})\n"
msgstr ""
~ianmdlvl / developers-reference.git / blobdiff