Re: Fwd: Bug#781847: RFS: python-tappy/1.3-1 [ITP] -- Test Anything Protocol (TAP) tools for Python

[Ben Finney <ben+debian@benfinney.id.au>]

Nicolas CANIART <nicolas@caniart.net> writes:

> Upstream ships its changelog as a reStructuredText file which is also
> included in the documentation. Should I put a copy of it in the binary
> packages anyway ?

Yes, the convention that the changelog will be installed as a plain-text
file named ‘/usr/share/doc/$PACKAGENAME/changelog.gz’ is part of Policy
§12.7.

For an upstream changelog distributed as reStructuredText, this is easy
enough to satisfy:

    #! /usr/bin/make -f
    # debian/rules

    # …

    override_dh_installchangelogs:
            dh_installchangelogs CHANGES.txt

>   (It would mean that up to 4 copies of it can get installed on a
>   system !)

One of which is in the location and format Policy expects it to be.

-- 
 \         “I think Western civilization is more enlightened precisely |
  `\     because we have learned how to ignore our religious leaders.” |
_o__)                                                —Bill Maher, 2003 |
Ben Finney