1 * Useful Makefile targets
3 The following 'make' targets exist for your convenience:
6 validate the well-formedness of all SGML materials
9 build all languages in all formats
11 make developers-reference.sgml.validate
12 validate the well-formedness of the English manual
14 make developers-reference.html
15 build the English manual
20 To contain the maintainers of this package, email
21 <developers-reference@packages.debian.org>.
26 If you want to contribute to the Developer's Reference, it's best to
27 first submit a few patches as bug reports. Writing patches for
28 existing bugs are also always appreciated. You may wish to make
29 patches against the CVS sources, about which see below.
31 Do not commit patches to the developers reference yourself unless
32 authorized to do so. Patches need to be finalized and common opinion
33 before they are applied.
38 If you're interested in ongoing maintenance, once you've shown that
39 you've mastered the style of the manual with a couple accepted
40 patches, you can be given CVS pserver access. If you have already
41 access to the CVS server for other reasons, do not use it unless
44 Instructions on how to get the CVS version of this software, including
45 how to get CVS access, can be found at
46 <URL:http://www.debian.org/doc/cvs>.
51 We have tried to keep language-independant bits of text in common.ent.
52 Feel free to truck stuff out of the English manual into common.ent if
53 it's useful, or else report the problem.
55 You should exploit CVS to see the diffs between when the document was
56 last translated and the latest version. Be sure to set the cvs-en-rev
57 entity as appropriate when you do update a translation.
59 We have provided commands to help with this. To see the difference in
60 numbers between the latest translated version and the latest version,
63 ./translation-status fr
65 To get the diff between the latest translated version and the latest
68 ./translation-status -d fr