X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=po4a%2Fja%2Fbest-pkging-practices.po;h=b23ab8a9bd6db9b588b192adf78164a6b1e01192;hb=e6ab4c663c7792c660d2639898a2b641f57f8106;hp=67a976229361021d8c6af42244e7f5ffe2fb264b;hpb=c0e2a26f7817b5396ee5267d2e678c4f95593b76;p=developers-reference.git diff --git a/po4a/ja/best-pkging-practices.po b/po4a/ja/best-pkging-practices.po index 67a9762..b23ab8a 100644 --- a/po4a/ja/best-pkging-practices.po +++ b/po4a/ja/best-pkging-practices.po @@ -4,7 +4,7 @@ msgid "" msgstr "" "Project-Id-Version: developers-reference 3.3.9\n" -"POT-Creation-Date: 2008-03-05 18:02+0900\n" +"POT-Creation-Date: 2008-06-14 14:14+0900\n" "PO-Revision-Date: 2008-03-05 18:30+0900\n" "Last-Translator: Hideki Yamane (Debian-JP) \n" "Language-Team: Debian JP Project \n" @@ -67,13 +67,13 @@ msgid "" "The rationale for using helper scripts in debian/rules " "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 /usr/lib/menu (or /" -"usr/lib/menu 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 to do, why " -"should each maintainer rewrite all this on their own, sometimes with bugs? " -"Also, supposing the menu directory changed, every package would have to be " -"changed." +"need to put the file into /usr/share/menu (or " +"/usr/lib/menu 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 " +"to do, why should each maintainer rewrite all this on their own, sometimes " +"with bugs? Also, supposing the menu directory changed, every package would " +"have to be changed." msgstr "" # type: Content of:
@@ -468,9 +468,9 @@ msgstr "" # type: Content of:
#: 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 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." msgstr "" # type: Content of:
@@ -829,28 +829,30 @@ msgstr "" # type: Content of:
#: 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 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." msgstr "" # type: Content of:
-#: best-pkging-practices.dbk:560 +#: 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 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:" msgstr "" # type: Content of:
-#: best-pkging-practices.dbk:567 +#: best-pkging-practices.dbk:570 #, no-wrap msgid "" "\n" @@ -865,30 +867,32 @@ msgid "" msgstr "" # type: Content of:
-#: best-pkging-practices.dbk:578 +#: 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 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." msgstr "" # type: Content of:
-#: best-pkging-practices.dbk:584 +#: 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 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!" msgstr "" # type: Content of:
-#: best-pkging-practices.dbk:605 +#: best-pkging-practices.dbk:610 msgid "Best practices for maintainer scripts" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:607 +#: best-pkging-practices.dbk:612 msgid "" "Maintainer scripts include the files <filename>debian/postinst</filename>, " "<filename>debian/preinst</filename>, <filename>debian/prerm</filename> and " @@ -899,7 +903,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:615 +#: 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 " @@ -907,14 +911,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:620 +#: 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:624 +#: 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 role=\"package" @@ -924,7 +928,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:631 +#: 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 " @@ -934,7 +938,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:638 +#: 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 " @@ -943,27 +947,27 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:644 +#: 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:647 +#: 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:649 +#: 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:654 +#: 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 " @@ -973,7 +977,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:661 +#: 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> " @@ -984,14 +988,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:671 +#: 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:673 +#: 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 " @@ -1002,7 +1006,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:681 +#: 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> <refentrytitle>debconf-devel</" @@ -1012,7 +1016,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><para> -#: best-pkging-practices.dbk:688 +#: 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 " @@ -1021,12 +1025,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:694 +#: best-pkging-practices.dbk:699 msgid "Do not abuse debconf" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:696 +#: 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 " @@ -1035,7 +1039,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:702 +#: 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 " @@ -1044,7 +1048,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:708 +#: best-pkging-practices.dbk:713 msgid "" "Carefully choose the questions priorities in maintainer scripts. See " "<citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</" @@ -1053,38 +1057,38 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:716 +#: 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:718 +#: best-pkging-practices.dbk:723 msgid "Write correct English" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:720 +#: 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:724 +#: 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:728 +#: 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:732 +#: 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 " @@ -1093,12 +1097,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:740 +#: best-pkging-practices.dbk:745 msgid "Be kind to translators" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:742 +#: 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 " @@ -1106,15 +1110,15 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:747 +#: 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)." +"(<literal>man po-debconf</literal> is a good start)." msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:752 +#: 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 " @@ -1126,22 +1130,23 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:761 +#: 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:766 +#: 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:771 +#: 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 " @@ -1151,12 +1156,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:780 +#: 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:782 +#: 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 role=\"strong" @@ -1165,21 +1170,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:788 +#: 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:792 +#: 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:798 +#: 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> " @@ -1187,7 +1192,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><programlisting> -#: best-pkging-practices.dbk:802 +#: best-pkging-practices.dbk:807 #, no-wrap msgid "" "for i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null\n" @@ -1195,7 +1200,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:807 +#: 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 " @@ -1203,7 +1208,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:814 +#: 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, " @@ -1211,41 +1216,41 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:821 +#: 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:827 +#: 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:829 +#: 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:833 +#: 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:838 +#: 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:845 +#: 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:847 +#: 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 " @@ -1253,7 +1258,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:852 +#: 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 " @@ -1262,19 +1267,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:858 +#: 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:864 +#: best-pkging-practices.dbk:869 msgid "Do not use first person" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:866 +#: 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 " @@ -1286,24 +1291,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:876 +#: best-pkging-practices.dbk:881 msgid "Be gender neutral" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:878 +#: 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:886 +#: best-pkging-practices.dbk:891 msgid "Templates fields definition" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:888 +#: best-pkging-practices.dbk:893 msgid "" "This part gives some information which is mostly taken from the " "<citerefentry> <refentrytitle>debconf-devel</refentrytitle> <manvolnum>7</" @@ -1311,28 +1316,28 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:893 +#: best-pkging-practices.dbk:898 msgid "Type" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:895 +#: best-pkging-practices.dbk:900 msgid "string:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:897 +#: 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:902 +#: best-pkging-practices.dbk:907 msgid "password:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:904 +#: 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 " @@ -1340,24 +1345,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:911 +#: best-pkging-practices.dbk:916 msgid "boolean:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:913 +#: 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:919 +#: best-pkging-practices.dbk:924 msgid "select:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:921 +#: 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 " @@ -1365,24 +1370,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:928 +#: best-pkging-practices.dbk:933 msgid "multiselect:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:930 +#: 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:936 +#: best-pkging-practices.dbk:941 msgid "note:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:938 +#: 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 " @@ -1392,22 +1397,22 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:947 +#: best-pkging-practices.dbk:952 msgid "text:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:949 +#: 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:954 +#: best-pkging-practices.dbk:959 msgid "error:" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:956 +#: 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 " @@ -1415,26 +1420,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><para> -#: best-pkging-practices.dbk:961 +#: 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:969 +#: best-pkging-practices.dbk:974 msgid "Description: short and extended description" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:971 +#: 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:975 +#: 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 " @@ -1443,7 +1448,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:981 +#: 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 " @@ -1452,14 +1457,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:987 +#: 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:991 +#: 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 " @@ -1469,7 +1474,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:998 +#: 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 " @@ -1477,7 +1482,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1003 +#: 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 " @@ -1486,26 +1491,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1009 +#: 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:1013 +#: 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:1019 +#: best-pkging-practices.dbk:1024 msgid "Choices" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1021 +#: 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 " @@ -1513,12 +1518,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1028 +#: best-pkging-practices.dbk:1033 msgid "Default" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1030 +#: 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 " @@ -1526,41 +1531,41 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1039 +#: best-pkging-practices.dbk:1044 msgid "Templates fields specific style guide" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1041 +#: best-pkging-practices.dbk:1046 msgid "Type field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1043 +#: 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:1049 +#: best-pkging-practices.dbk:1054 msgid "Description field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1051 +#: 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:1055 +#: 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:1059 +#: 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 Address?) in favour of " @@ -1568,7 +1573,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1066 +#: 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 " @@ -1577,12 +1582,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:1076 +#: best-pkging-practices.dbk:1081 msgid "Boolean templates" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1080 +#: 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 " @@ -1591,19 +1596,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1088 +#: 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:1096 +#: best-pkging-practices.dbk:1101 msgid "Select/Multiselect" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1100 +#: best-pkging-practices.dbk:1105 msgid "" "The short description is a prompt and <emphasis role=\"strong\">not</" "emphasis> a title. Do <emphasis role=\"strong\">not</emphasis> use useless " @@ -1612,7 +1617,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1108 +#: 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 " @@ -1621,24 +1626,24 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><section><title> -#: best-pkging-practices.dbk:1118 +#: best-pkging-practices.dbk:1123 msgid "Notes" msgstr "" # type: Content of: <chapter><section><section><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1122 +#: 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:1127 +#: 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:1133 +#: 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: " @@ -1650,12 +1655,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1148 +#: best-pkging-practices.dbk:1153 msgid "Choices field" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1150 +#: 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 " @@ -1663,12 +1668,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1157 best-pkging-practices.dbk:1195 +#: 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:1159 +#: 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 " @@ -1676,7 +1681,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1164 +#: 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 " @@ -1685,12 +1690,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1170 +#: 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:1172 +#: best-pkging-practices.dbk:1177 #, no-wrap msgid "" "\n" @@ -1706,7 +1711,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1184 +#: 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 " @@ -1714,21 +1719,21 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1189 +#: 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:1197 +#: 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:1201 +#: 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 " @@ -1736,7 +1741,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1206 +#: 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 " @@ -1745,17 +1750,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:1218 +#: best-pkging-practices.dbk:1223 msgid "Internationalization" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1220 +#: best-pkging-practices.dbk:1225 msgid "Handling debconf translations" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1222 +#: 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 " @@ -1764,7 +1769,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1228 +#: 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, " @@ -1777,7 +1782,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1238 +#: best-pkging-practices.dbk:1243 msgid "" "Using <systemitem role=\"package\">po-debconf</systemitem>, the translation " "is stored in <filename>po</filename> files (drawing from <command>gettext</" @@ -1793,12 +1798,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1254 +#: best-pkging-practices.dbk:1259 msgid "Internationalized documentation" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1256 +#: 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 " @@ -1806,7 +1811,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1261 +#: 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 " @@ -1823,7 +1828,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1275 +#: 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 " @@ -1832,17 +1837,17 @@ msgid "" msgstr "" # type: Content of: <chapter><section><title> -#: best-pkging-practices.dbk:1285 +#: best-pkging-practices.dbk:1290 msgid "Common packaging situations" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1296 +#: 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:1298 +#: 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, " @@ -1855,12 +1860,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1310 +#: best-pkging-practices.dbk:1315 msgid "Libraries" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1312 +#: 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 " @@ -1869,26 +1874,26 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1318 +#: 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:1325 +#: best-pkging-practices.dbk:1330 msgid "Documentation" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1327 +#: 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:1332 +#: 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 " @@ -1896,7 +1901,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1337 +#: 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 " @@ -1906,7 +1911,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1344 +#: best-pkging-practices.dbk:1349 msgid "" "Major shipped manuals should register themselves with <systemitem role=" "\"package\">doc-base</systemitem> on installation. See the <systemitem role=" @@ -1914,19 +1919,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1352 +#: best-pkging-practices.dbk:1357 msgid "Specific types of packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1354 +#: 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:1360 +#: 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 <systemitem role=" @@ -1935,28 +1940,28 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1369 +#: 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:1376 +#: 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:1383 +#: 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:1390 +#: 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 " @@ -1965,14 +1970,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1398 +#: 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> package." msgstr "" # type: Content of: <chapter><section><section><itemizedlist><listitem><para> -#: best-pkging-practices.dbk:1404 +#: best-pkging-practices.dbk:1409 msgid "" "Lisp packages should register themselves with <systemitem role=\"package" "\">common-lisp-controller</systemitem>, about which see &file-lisp-" @@ -1980,12 +1985,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1434 +#: best-pkging-practices.dbk:1439 msgid "Architecture-independent data" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1436 +#: 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, " @@ -1995,7 +2000,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1443 +#: 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 " @@ -2003,25 +2008,24 @@ msgid "" "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:1455 +#: best-pkging-practices.dbk:1460 msgid "Needing a certain locale during build" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1457 +#: 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:1461 +#: 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 name of the " @@ -2030,7 +2034,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1465 +#: best-pkging-practices.dbk:1470 #, no-wrap msgid "" "\n" @@ -2046,12 +2050,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1479 +#: best-pkging-practices.dbk:1484 msgid "Make transition packages deborphan compliant" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1481 +#: 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 " @@ -2061,16 +2065,16 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1488 +#: 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:1494 +#: 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: " @@ -2079,32 +2083,32 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1502 +#: 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:1504 +#: 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:1508 +#: best-pkging-practices.dbk:1514 msgid "Pristine source" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote> -#: best-pkging-practices.dbk:1510 +#: 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>" +"The defining characteristic of a pristine source tarball is that the " +"<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:1512 +#: 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 " @@ -2113,13 +2117,13 @@ msgid "" "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." +"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:1522 +#: 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 " @@ -2129,7 +2133,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1530 +#: 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 <command>dpkg-" @@ -2138,12 +2142,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1538 +#: 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:1540 +#: best-pkging-practices.dbk:1546 #, no-wrap msgid "" "\n" @@ -2151,7 +2155,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1546 +#: 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 " @@ -2161,7 +2165,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1555 +#: 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, " @@ -2171,12 +2175,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1566 +#: best-pkging-practices.dbk:1572 msgid "Repackaged upstream source" msgstr "upstream のソースをパッケージしなおす" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1568 +#: 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 " @@ -2186,19 +2190,19 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1575 +#: best-pkging-practices.dbk:1581 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 <literal><debian-" -"revision></literal>." +"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:1584 +#: 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 " @@ -2210,12 +2214,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1593 -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:1598 +#: 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 " @@ -2227,7 +2231,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote> -#: best-pkging-practices.dbk:1610 +#: 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 " @@ -2236,7 +2240,7 @@ msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para><footnote><para> #. or similarly named -#: best-pkging-practices.dbk:1612 +#: 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 " @@ -2248,12 +2252,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1619 +#: best-pkging-practices.dbk:1625 msgid "</footnote>" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1624 +#: best-pkging-practices.dbk:1630 msgid "" "<emphasis role=\"strong\">should</emphasis>, except where impossible for " "legal reasons, preserve the entire building and portablility infrastructure " @@ -2265,7 +2269,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1633 +#: 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 " @@ -2273,7 +2277,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1640 +#: best-pkging-practices.dbk:1646 msgid "" "<emphasis role=\"strong\">should</emphasis> use <literal><packagename>-" "<upstream-version>.orig</literal> as the name of the top-level " @@ -2282,14 +2286,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><orderedlist><listitem><para> -#: best-pkging-practices.dbk:1648 +#: 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:1653 +#: 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 unpacked " @@ -2297,12 +2301,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><title> -#: best-pkging-practices.dbk:1659 +#: 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:1661 +#: 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 " @@ -2315,7 +2319,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para><footnote><para> -#: best-pkging-practices.dbk:1668 +#: 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 " @@ -2326,14 +2330,14 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><section><para> -#: best-pkging-practices.dbk:1676 +#: 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:1682 +#: 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 " @@ -2345,12 +2349,12 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><title> -#: best-pkging-practices.dbk:1695 +#: best-pkging-practices.dbk:1701 msgid "Best practices for debug packages" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1697 +#: 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 " @@ -2361,7 +2365,7 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1705 +#: 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 " @@ -2374,48 +2378,50 @@ msgid "" msgstr "" # type: Content of: <chapter><section><section><para> -#: best-pkging-practices.dbk:1715 +#: 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 " -"<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>." +"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:1727 +#: 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:1734 +#: 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:1741 +#: 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 example:" msgstr "" # type: Content of: <chapter><section><section><screen> -#: best-pkging-practices.dbk:1744 +#: best-pkging-practices.dbk:1751 #, fuzzy, no-wrap msgid "" "\n"