</para>
<para>
You should periodically get the newest <systemitem
-role="package">lintian</systemitem> from `unstable' and check over all your
-packages. Notice that the <literal>-i</literal> 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</systemitem> from <literal>unstable</literal> and check
+over all your packages. Notice that the <literal>-i</literal> 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.
</para>
<para>
Refer to <xref linkend="sanitycheck"/> for more information on how and when to
You can also see a summary of all problems reported by Lintian on your packages
at <ulink url="&url-lintian;"></ulink>. These reports contain the
latest <command>lintian</command> output for the whole development distribution
-(unstable).
-</para>
-</section>
-
-<section id="linda">
-<title><systemitem role="package">linda</systemitem></title>
-<para>
-<systemitem role="package">linda</systemitem> is another package linter. It is
-similar to <systemitem role="package">lintian</systemitem> but has a different
-set of checks. Its written in Python rather than Perl.
+(<literal>unstable</literal>).
</para>
</section>
</para>
</section>
-<section id="debmake">
-<title><systemitem role="package">debmake</systemitem></title>
-<para>
-<systemitem role="package">debmake</systemitem>, a precursor to <systemitem
-role="package">debhelper</systemitem>, is a more coarse-grained
-<filename>debian/rules</filename> assistant. It includes two main programs:
-<command>deb-make</command>, which can be used to help a maintainer convert a
-regular (non-Debian) source archive into a Debian source package; and
-<command>debstd</command>, which incorporates in one big shot the same sort of
-automated functions that one finds in <systemitem
-role="package">debhelper</systemitem>.
-</para>
-<para>
-The consensus is that <systemitem role="package">debmake</systemitem> is now
-deprecated in favor of <systemitem role="package">debhelper</systemitem>. It
-is a bug to use <systemitem role="package">debmake</systemitem> in new
-packages. New packages using <systemitem role="package">debmake</systemitem>
-will be rejected from the archive.
-</para>
-</section>
-
<section id="dh-make">
<title><systemitem role="package">dh-make</systemitem></title>
<para>
<para>
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 <emphasis>stable</emphasis>, <emphasis>unstable</emphasis> and possibly
-<emphasis>experimental</emphasis> distributions, along with the other benefits
+for <literal>stable</literal>, <literal>unstable</literal> and possibly
+<literal>experimental</literal> distributions, along with the other benefits
of a version control system.
</para>
</section>
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 <xref linkend="buildd"/> for more information, and <ulink
-url="&url-buildd;"></ulink> to see the system in action.
+architectures. See <xref linkend="wanna-build"/> for more information, and
+<ulink url="&url-buildd;"></ulink> to see the system in action.
</para>
</section>
The following packages provide information for maintainers or help with
building documentation.
</para>
+
+<section id="docbook-xml">
+<title><systemitem role="package">docbook-xml</systemitem></title>
+<para>
+<systemitem role="package">docbook-xml</systemitem> 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.
+</para>
+<para>
+The <systemitem role="package">docbook-xsl</systemitem> package
+provides the XSL files for building and styling the source to various
+output formats. You will need an XSLT processor, such as <systemitem
+role="package">xsltproc</systemitem>, to use the XSL stylesheets.
+Documentation for the stylesheets can be found in the various
+<systemitem role="package">docbook-xsl-doc-*</systemitem> packages.
+</para>
+<para>
+To produce PDF from FO, you need an FO processor, such as <systemitem
+role="package">xmlroff</systemitem> or <systemitem
+role="package">fop</systemitem>. Another tool to generate PDF from
+DocBook XML is <systemitem role="package">dblatex</systemitem>.
+</para>
+</section>
+
<section id="debiandoc-sgml">
<title><systemitem role="package">debiandoc-sgml</systemitem></title>
<para>
<systemitem role="package">debiandoc-sgml</systemitem> 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
+(<systemitem role="package">docbook-xml</systemitem>
+should be used instead).
+It also provides scripts for building and
styling the source to various output formats.
</para>
<para>
</para>
</section>
+<section id="debian-maintainers">
+<title><systemitem role="package">debian-maintainers</systemitem></title>
+<para>
+Contains the public GPG keys of Debian Maintainers.
+See <ulink url="&url-wiki-dm;"></ulink> for more information.
+</para>
+</section>
+
<section id="debview">
<title><systemitem role="package">debview</systemitem></title>
<para>
~ianmdlvl / developers-reference.git / blobdiff