Commit 9dd53eef authored by Jelmer Vernooij's avatar Jelmer Vernooij

Add more notes on writing fixers, add anchors.

parent c7506efe
......@@ -15,6 +15,8 @@ lintian-brush
in the top-level of your (version controlled) Debian package.
.. _supported-tags:
Supported tags
--------------
......@@ -56,6 +58,8 @@ subset of the issues:
* xs-testsuite-field-in-debian-control
* xs-vcs-field-in-debian-control
.. _writing-fixers:
Writing new fixers
------------------
......@@ -81,3 +85,9 @@ It can include optional metadata in its output::
* ``Certainty:`` followed by ``certain`` or ``possible``,
indicating how certain the fixer is that the fix was the right
one.
The easiest way to test fixers is to create a skeleton *in* and *out* source tree under
``tests/FIXER-NAME/TEST-NAME``. The ``in`` directory should contain the tree to
run the fixer on,and ``out`` contains the directory after it has run. It's fine
to create directories with only one or two control files, if the fixer only
needs those.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment