Re: DEP-5 (copyright file format) ... gap with practice
Hi,
On Wed, Sep 10, 2014 at 10:20:06AM +0200, Stefano Zacchiroli wrote:
> How about using your snippet to improve our packaging work-flows
> instead? For instance, we can have a lintian check that verifies if
> those files are present in the source package and emit a warning if they
> are not listed (with the correct license) in debian/copyright.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The debmake command (in python) offers such copyright file verification
against the current source files by running it in the source tree as.
$ debmake -k
Its manpage goes as:
-k, --kludge
compare the debian/copyright file with the source and exit.
The debian/copyright file must be organized to list the generic
file patterns before the specific exceptions.
· -k: basic output style
· -kk: verbose output style
It will most likely give you a nice list of such files noting changes of
license and missing licenses.
I am wondering if it is really useful or not for the case of
auto-generated permissive files. If dropping those files is the
accepted standard behavior (even if it is not codified after this
discussion), I am thinking of dropping those files from the emitted
default output list of -k and template copyright file it generates
unless specifically asked.
Osamu
PS:
The copyright phrase parser of the debmake command is much tighter than
the licensecheck (in perl) one.
Reply to: