X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=tools.dbk;h=a9b4b816da0f35085f559c3529edcfbd3dfcda43;hp=de5cfd4b13f639da4e42fd3772aa6ed29a1f28b9;hb=cb8ca9a900618cb2f54a3311378294d549653b37;hpb=24edeec3ea3aef827fc6c23b59bafec1f5343593 diff --git a/tools.dbk b/tools.dbk index de5cfd4..a9b4b81 100644 --- a/tools.dbk +++ b/tools.dbk @@ -1,6 +1,8 @@ + "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [ + %commondata; +]> Overview of Debian Maintainer Tools @@ -24,7 +26,7 @@ exclusion of a competing tool. Most of the descriptions of these packages come from the actual package descriptions themselves. Further information can be found in the package documentation itself. You can also see more info with the command -apt-cache show <package-name>. +apt-cache show <package-name>.
Core tools @@ -93,10 +95,10 @@ errors. You should periodically get the newest lintian from `unstable' and check over all your -packages. Notice that the -i option provides detailed -explanations of what each error or warning means, what its basis in Policy is, -and commonly how you can fix the problem. +role="package">lintian from unstable and check +over all your packages. Notice that the -i option provides +detailed explanations of what each error or warning means, what its basis in +Policy is, and commonly how you can fix the problem. Refer to for more information on how and when to @@ -104,18 +106,9 @@ use Lintian. You can also see a summary of all problems reported by Lintian on your packages -at . These reports contain the +at . These reports contain the latest lintian output for the whole development distribution -(unstable). - -
- -
-<systemitem role="package">linda</systemitem> - -linda is another package linter. It is -similar to lintian but has a different -set of checks. Its written in Python rather than Perl. +(unstable).
@@ -134,13 +127,13 @@ help you prevent various accidents. You can run it over a pair of binary packages: - package_1-1_arch.deb package_2-1_arch.deb +debdiff package_1-1_arch.deb package_2-1_arch.deb Or even a pair of changes files: - package_1-1_arch.changes package_2-1_arch.changes +debdiff package_1-1_arch.changes package_2-1_arch.changes For more information please see @@ -269,8 +262,8 @@ upstream changes into the repository. These utilities provide an infrastructure to facilitate the use of CVS by Debian maintainers. This allows one to keep separate CVS branches of a package -for stable, unstable and possibly -experimental distributions, along with the other benefits +for stable, unstable and possibly +experimental distributions, along with the other benefits of a version control system. @@ -313,8 +306,8 @@ environment. It can use chrooted environments as well. It can be used stand-alone, or as part of a networked, distributed build environment. As the latter, it is part of the system used by porters to build binary packages for all the available -architectures. See for more information, and to see the system in action. +architectures. See for more information, and + to see the system in action. @@ -457,7 +450,7 @@ process through dpkg-depcheck will provide you with a good first approximation of the build-dependencies. For example: --depcheck -b debian/rules build +dpkg-depcheck -b debian/rules build dpkg-depcheck can also be used to check for run-time @@ -506,12 +499,40 @@ enhanced to support cross-compiling. The following packages provide information for maintainers or help with building documentation. + +
+<systemitem role="package">docbook-xml</systemitem> + +docbook-xml provides the +DocBook XML DTDs, which are commonly used for Debian documentation (as +is the older debiandoc SGML DTD). This manual, for instance, is +written in DocBook XML. + + +The docbook-xsl package +provides the XSL files for building and styling the source to various +output formats. You will need an XSLT processor, such as xsltproc, to use the XSL stylesheets. +Documentation for the stylesheets can be found in the various +docbook-xsl-doc-* packages. + + +To produce PDF from FO, you need an FO processor, such as xmlroff or fop. Another tool to generate PDF from +DocBook XML is dblatex. + +
+
<systemitem role="package">debiandoc-sgml</systemitem> debiandoc-sgml provides the DebianDoc -SGML DTD, which is commonly used for Debian documentation. This manual, for -instance, is written in DebianDoc. It also provides scripts for building and +SGML DTD, which is commonly used for Debian documentation, +but is now deprecated +(docbook-xml +should be used instead). +It also provides scripts for building and styling the source to various output formats. @@ -528,6 +549,14 @@ linkend="key-maint"/> and the package documentation for more information.
+
+<systemitem role="package">debian-maintainers</systemitem> + +Contains the public GPG keys of Debian Maintainers. +See for more information. + +
+
<systemitem role="package">debview</systemitem>