[SCM] Debian package checker branch, master, updated. 2.5.1-40-g4a7b371
The following commit has been merged in the master branch:
commit 4a7b37126a128c3494106aefd6bef935f50a31d7
Author: Niels Thykier <niels@thykier.net>
Date: Fri Jul 8 01:19:19 2011 +0200
Updated the Lintian User Manual
diff --git a/debian/changelog b/debian/changelog
index 0089b71..99c3b1f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -97,6 +97,9 @@ lintian (2.5.2) UNRELEASED; urgency=low
* doc/lintian.xml:
+ [NT] Added information about the new Vendor profiles.
+ + [NT] Improved various parts of the User Manual. Especially
+ mention that Lintian can be run on changes files and this
+ processes all packages related to the changes file.
* frontend/{lintian,lintian-info}:
+ [NT] Added profile support (new option --profile), please
diff --git a/doc/lintian.xml b/doc/lintian.xml
index 94d2965..8468e64 100644
--- a/doc/lintian.xml
+++ b/doc/lintian.xml
@@ -279,13 +279,26 @@
the <systemitem role="package">lintian</systemitem> Debian
package.
</para>
+ <para>
+ Alternatively you can checkout Lintian from the source
+ repository and use that directly. By setting LINTIAN_ROOT (or
+ using the --root option) lintian can be run from the source
+ directory as if it had been installed on your system.
+ </para>
+ <para>
+ The only known caveat of using Lintian from the source
+ directory is that Lintian requires a C.UTF-8 (or en_US.UTF-8)
+ locale to correctly process some files.
+ The <systemitem role="package">lintian</systemitem> Debian
+ package will set up this locale during installation.
+ </para>
</sect1>
<sect1 label="2.2" id="section-2.2">
<title>Running lintian</title>
<para>
- After that, you can run Lintian over any Debian binary, udeb
- or source packages like this:
+ After that, you can run Lintian on a changes file or any
+ Debian binary, udeb or source packages like this:
</para>
<screen>
$ lintian libc5_5.4.38-1.deb
@@ -299,16 +312,28 @@ E: libc5: shlib-missing-in-control-file libgnumalloc usr/lib/libgnumalloc.so.5.4
$
</screen>
<para>
- As you can see, Lintian uses a special format for all its
- error and warning messages. With that, its very easy to write
- other programs which run Lintian and interpret the displayed
- messages.
+ Please note that some checks are cross-package checks and can
+ only be (accurately) performed if the binary packages and the
+ source are processed together. If Lintian is passed a changes
+ file, it will attempt to process all packages listed in the
+ changes file.
+ </para>
+ <para>
+ Lintian supports a number of command line options, which are
+ documented in the manpage of lintian(1). Some of the options
+ may appear in the lintianrc file (without the leading dashes)
+ in Lintian 2.5.1 (or newer).
</para>
</sect1>
<sect1 label="2.3" id="section-2.3">
<title>Lintian Tags</title>
<para>
+ Lintian uses a special format for all its error and warning
+ messages. With that it is very easy to write other programs
+ which run Lintian and interpret the displayed messages.
+ </para>
+ <para>
The first character of each line indicates the type of
message. Currently, the following types are supported:
</para>
@@ -472,12 +497,19 @@ $
sure the problem is not actually a bug in Lintian or an error in the author's
reading of policy. Please do not override bugs in lintian, they should rather
be fixed than overridden.
+ </para>
+ <para>
Once it has been decided that an override is needed, you can easily add one by
supplying an overrides file. If the override is for a binary or udeb
package, you have to place it at
<filename>/usr/share/lintian/overrides/<replaceable><package></replaceable></filename>
- inside the package. If the override is for a source package,
- you have to place it
+ inside the package. The tool <command>dh_lintian</command>
+ from the Debian
+ package <systemitem role="package">debhelper</systemitem> may
+ be useful for this purpose.
+ </para>
+ <para>
+ If the override is for a source package, you have to place it
at <filename>debian/source/lintian-overrides</filename>
or <filename>debian/source.lintian-overrides</filename> (the
former path is preferred). With that, Lintian will know about
--
Debian package checker
Reply to: