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
-<command>apt-cache show <package-name></command>.
+<command>apt-cache show <literal>package-name</literal></command>.
</para>
<section id="tools-core">
<title>Core tools</title>
</para>
<para>
Many feel that this system should be used for all packages which require
-interactive configuration; see <xref linkend="bpp-config-mgmt"/> . <systemitem
+interactive configuration; see <xref linkend="bpp-config-mgmt"/>. <systemitem
role="package">debconf</systemitem> is not currently required by Debian Policy,
but that may change in the future.
</para>
</section>
<section id="debdiff">
-<title><systemitem role="package">debdiff</systemitem></title>
+<title><command>debdiff</command></title>
<para>
<command>debdiff</command> (from the <systemitem
-role="package">devscripts</systemitem> package, <xref linkend="devscripts"/> )
+role="package">devscripts</systemitem> package, <xref linkend="devscripts"/>)
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
<command>dh_make</command>, a program that creates a skeleton of files
necessary to build a Debian package out of a source tree. As the name
suggests, <command>dh_make</command> is a rewrite of <systemitem
-role="package">debmake</systemitem> and its template files use dh_* programs
+role="package">debmake</systemitem> and its template files use <command>dh_*</command> programs
from <systemitem role="package">debhelper</systemitem>.
</para>
<para>
SPECS files from RPM source packages.
</para>
<para>
-For more informations see <literal><ulink
-url="http://yada.alioth.debian.org/">YADA site</ulink></literal>.
+For more informations see <ulink
+url="http://yada.alioth.debian.org/"><literal>YADA</literal> site</ulink>.
</para>
</section>
</section>
<section id="dcut">
-<title><systemitem role="package">dcut</systemitem></title>
+<title><command>dcut</command></title>
<para>
-The <systemitem role="package">dcut</systemitem> script (part of the package
-<xref linkend="dput"/> ) helps in removing files from the ftp upload directory.
+The <command>dcut</command> script (part of the package <systemitem role="package">dput</systemitem>,
+<xref linkend="dput"/>) helps in removing files from the ftp upload directory.
</para>
</section>
</section>
<section id="dpkg-depcheck">
-<title><systemitem role="package">dpkg-depcheck</systemitem></title>
+<title><command>dpkg-depcheck</command></title>
<para>
<command>dpkg-depcheck</command> (from the <systemitem
-role="package">devscripts</systemitem> package, <xref linkend="devscripts"/> )
+role="package">devscripts</systemitem> package, <xref linkend="devscripts"/>)
runs a command under <command>strace</command> to determine all the packages
that were used by the said command.
</para>
</screen>
<para>
<command>dpkg-depcheck</command> 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 <citerefentry>
+<refentrytitle>exec</refentrytitle> <manvolnum>2</manvolnum> </citerefentry>
+to run other programs.
</para>
<para>
For more information please see <citerefentry>