/[ddp]/manuals/trunk/developers-reference/best-pkging-practices.dbk
ViewVC logotype

Diff of /manuals/trunk/developers-reference/best-pkging-practices.dbk

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 4910 by debacle, Sat Jun 30 13:21:18 2007 UTC revision 4911 by debacle, Sun Jul 1 11:50:47 2007 UTC
# Line 1  Line 1 
1  <?xml version="1.0" encoding="utf-8"?>  <?xml version="1.0" encoding="utf-8"?>
2  <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"  <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3      "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [      "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
4    <!ENTITY % commondata  SYSTEM "common.ent" > %commondata;    <!ENTITY % commondata SYSTEM "common.ent" > %commondata;
5  ]>  ]>
6  <chapter id="best-pkging-practices">  <chapter id="best-pkging-practices">
7  <title>Best Packaging Practices</title>  <title>Best Packaging Practices</title>
# Line 80  Some people feel that vanilla <filename> Line 80  Some people feel that vanilla <filename>
80  better, since you don't have to learn the intricacies of any helper system.  better, since you don't have to learn the intricacies of any helper system.
81  This decision is completely up to you.  Use what works for you.  Many examples  This decision is completely up to you.  Use what works for you.  Many examples
82  of vanilla <filename>debian/rules</filename> files are available at <ulink  of vanilla <filename>debian/rules</filename> files are available at <ulink
83  url="http://arch.debian.org/arch/private/srivasta/"></ulink>.  url="&url-rules-files;"></ulink>.
84  </para>  </para>
85  </section>  </section>
86    
# Line 203  Postscript or postscript. Line 203  Postscript or postscript.
203  </para>  </para>
204  <para>  <para>
205  If you are having problems writing your description, you may wish to send it  If you are having problems writing your description, you may wish to send it
206  along to <email>debian-l10n-english@&lists-host;</email> and request  along to &email-debian-l10n-english; and request feedback.
 feedback.  
207  </para>  </para>
208  </section>  </section>
209    
# Line 343  added at the end of description, using t Line 342  added at the end of description, using t
342  <para>  <para>
343  Note the spaces prepending the line, which serves to break the lines correctly.  Note the spaces prepending the line, which serves to break the lines correctly.
344  To see an example of how this displays, see <ulink  To see an example of how this displays, see <ulink
345  url="http://&packages-host;/unstable/web/wml"></ulink>.  url="&url-eg-desc-upstream-info;"></ulink>.
346  </para>  </para>
347  <para>  <para>
348  If there is no home page for the software, this should naturally be left out.  If there is no home page for the software, this should naturally be left out.
# Line 740  Most Debian package maintainers are not Line 739  Most Debian package maintainers are not
739  properly phrased templates may not be easy for them.  properly phrased templates may not be easy for them.
740  </para>  </para>
741  <para>  <para>
742  Please use (and abuse) <email>debian-l10n-english@&lists-host;</email>  Please use (and abuse) &email-debian-l10n-english; mailing
743  mailing list.  Have your templates proofread.  list.  Have your templates proofread.
744  </para>  </para>
745  <para>  <para>
746  Badly written templates give a poor image of your package, of your work...or  Badly written templates give a poor image of your package, of your work...or
# Line 784  translations and request them for update Line 783  translations and request them for update
783  <para>  <para>
784  If in doubt, you may also contact the translation team for a given language  If in doubt, you may also contact the translation team for a given language
785  (debian-l10n-xxxxx@&lists-host;), or the  (debian-l10n-xxxxx@&lists-host;), or the
786  <email>debian-i18n@&lists-host;</email> mailing list.  &email-debian-i18n; mailing list.
787  </para>  </para>
788  <para>  <para>
789  Calls for translations posted to <email>debian-i18n@&lists-host;</email>  Calls for translations posted to &email-debian-i18n; with the
790  with the <filename>debian/po/templates.pot</filename> file attached or  <filename>debian/po/templates.pot</filename> file attached or referenced in a
791  referenced in a URL are encouraged.  Be sure to mentions in these calls for new  URL are encouraged.  Be sure to mentions in these calls for new translations
792  translations which languages you have existing translations for, in order to  which languages you have existing translations for, in order to avoid duplicate
793  avoid duplicate work.  work.
794  </para>  </para>
795  </section>  </section>
796    
# Line 1283  differences between two versions of the Line 1282  differences between two versions of the
1282  can see what needs to be retranslated.  It is recommended that the translated  can see what needs to be retranslated.  It is recommended that the translated
1283  documentation maintain a note about what source control revision the  documentation maintain a note about what source control revision the
1284  translation is based on.  An interesting system is provided by <ulink  translation is based on.  An interesting system is provided by <ulink
1285  url="&url-cvsweb;boot-floppies/documentation/doc-check?rev=HEAD\|[amp  url="&url-i18n-doc-check;">doc-check</ulink> in the
1286  ]\|content-type=text/vnd.viewcvs-markup">doc-check</ulink> in the <systemitem  <systemitem role="package">boot-floppies</systemitem> package, which shows an
1287  role="package">boot-floppies</systemitem> package, which shows an overview of  overview of the translation status for any given language, using structured
1288  the translation status for any given language, using structured comments for  comments for the current revision of the file to be translated and, for a
1289  the current revision of the file to be translated and, for a translated file,  translated file, the revision of the original file the translation is based on.
1290  the revision of the original file the translation is based on.  You might wish  You might wish to adapt and provide that in your CVS area.
 to adapt and provide that in your CVS area.  
1291  </para>  </para>
1292  <para>  <para>
1293  If you maintain XML or SGML documentation, we suggest that you isolate any  If you maintain XML or SGML documentation, we suggest that you isolate any
# Line 1387  role="package">libmldbm-perl</systemitem Line 1385  role="package">libmldbm-perl</systemitem
1385  <listitem>  <listitem>
1386  <para>  <para>
1387  Python related packages have their python policy; see  Python related packages have their python policy; see
1388  <filename>/usr/share/doc/python/python-policy.txt.gz</filename> in the  &file-python-policy; in the <systemitem
1389  <systemitem role="package">python</systemitem> package.  role="package">python</systemitem> package.
1390  </para>  </para>
1391  </listitem>  </listitem>
1392  <listitem>  <listitem>
# Line 1408  policy</ulink>. Line 1406  policy</ulink>.
1406  <listitem>  <listitem>
1407  <para>  <para>
1408  Ocaml related packages have their own policy, found in  Ocaml related packages have their own policy, found in
1409  <filename>/usr/share/doc/ocaml/ocaml_packaging_policy.gz</filename> from the  &file-ocaml-policy; from the <systemitem
1410  <systemitem role="package">ocaml</systemitem> package.  A good example is the  role="package">ocaml</systemitem> package.  A good example is the <systemitem
1411  <systemitem role="package">camlzip</systemitem> source package.  role="package">camlzip</systemitem> source package.
1412  </para>  </para>
1413  </listitem>  </listitem>
1414  <listitem>  <listitem>
# Line 1478  If you need a certain locale during buil Line 1476  If you need a certain locale during buil
1476  this trick:  this trick:
1477  </para>  </para>
1478  <para>  <para>
1479  If you set <varname>LOCPATH</varname> to the equivalent of <literal>/usr/lib/locale</literal>, and <varname>LC_ALL</varname> to the name  If you set <varname>LOCPATH</varname> to the equivalent of <filename>/usr/lib/locale</filename>, and <varname>LC_ALL</varname> to the name
1480  of the locale you generate, you should get what you want without being root.  of the locale you generate, you should get what you want without being root.
1481  Something like this:  Something like this:
1482  </para>  </para>
Legend:
Removed from v.4910  
changed lines
  Added in v.4911
  ViewVC Help
Powered by ViewVC 1.1.5