X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=tools.dbk;h=c2b26a1eb6fb8211f8d57234b55a2662c4bd4d53;hb=c42d5ef4b193ae79b912626ff70f9d972847095d;hp=7f6264824884f7aff730e212966bc8c34e9b35bd;hpb=e3cb6d3f6afc7f8ed94ea6021aa0f9b4fa0e5551;p=developers-reference.git
diff --git a/tools.dbk b/tools.dbk
index 7f62648..c2b26a1 100644
--- a/tools.dbk
+++ b/tools.dbk
@@ -26,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.
-
-
-linda
-
-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).
-debdiff
+debdiff
debdiff (from the devscripts package, )
+role="package">devscripts package, )
compares file lists and control files of two packages. It is a simple
regression test, as it will help you notice if the number of binary packages
has changed since the last upload, or if something has changed in the control
@@ -184,27 +175,6 @@ them by doing apt-cache search ^dh-.
-
-debmake
-
-debmake, a precursor to debhelper, is a more coarse-grained
-debian/rules assistant. It includes two main programs:
-deb-make, which can be used to help a maintainer convert a
-regular (non-Debian) source archive into a Debian source package; and
-debstd, which incorporates in one big shot the same sort of
-automated functions that one finds in debhelper.
-
-
-The consensus is that debmake is now
-deprecated in favor of debhelper. It
-is a bug to use debmake in new
-packages. New packages using debmake
-will be rejected from the archive.
-
-
-
dh-make
@@ -212,7 +182,7 @@ The dh-make package contains
dh_make, a program that creates a skeleton of files
necessary to build a Debian package out of a source tree. As the name
suggests, dh_make is a rewrite of debmake and its template files use dh_* programs
+role="package">debmake and its template files use dh_* programs
from debhelper.
@@ -236,8 +206,8 @@ files. There is possibility to use macro engine similar to the one used in
SPECS files from RPM source packages.
-For more informations see YADA site.
+For more informations see YADA site.
@@ -271,8 +241,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.
@@ -315,8 +285,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.
@@ -351,10 +321,10 @@ signature and checksums before uploading, and the possibility of running
-dcut
+dcut
-The dcut script (part of the package
- ) helps in removing files from the ftp upload directory.
+The dcut script (part of the package dput,
+) helps in removing files from the ftp upload directory.
@@ -445,10 +415,10 @@ latest entry in a debian/changelog file.
-dpkg-depcheck
+dpkg-depcheck
dpkg-depcheck (from the devscripts package, )
+role="package">devscripts package, )
runs a command under strace to determine all the packages
that were used by the said command.
@@ -463,7 +433,9 @@ dpkg-depcheck -b debian/rules build
dpkg-depcheck can also be used to check for run-time
-dependencies, especially if your package uses exec(2) to run other programs.
+dependencies, especially if your package uses
+exec 2
+to run other programs.
For more information please see
@@ -508,12 +480,40 @@ enhanced to support cross-compiling.
The following packages provide information for maintainers or help with
building documentation.
+
+
+docbook-xml
+
+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.
+
+
+
debiandoc-sgml
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.
@@ -521,22 +521,6 @@ Documentation for the DTD can be found in the debiandoc-sgml-doc package.
-
debian-keyring
@@ -546,6 +530,14 @@ linkend="key-maint"/> and the package documentation for more information.
+
+debian-maintainers
+
+Contains the public GPG keys of Debian Maintainers.
+See for more information.
+
+
+