I think checking line length for the license text block would be much
more discriminative: approx 9% of the 317 currently matching packages
would trigger the test (some more than once). I attempted to simulate
this change in Lintian with a totally separate hacky script, manually
checking over the
Hi folks, sorry for the delay in getting involved.
On Tue, Aug 28, 2018 at 07:43:46AM +0100, Chris Lamb wrote:
Perhaps just looking at the size of the license text (say < 20 lines)
would work better? I don't know perl at all, so I can't help write it,
but I would be quite surprised if that
tags 906284 + moreinfo
thanks
Hi Julien,
> Perhaps just looking at the size of the license text (say < 20 lines)
> would work better? I don't know perl at all, so I can't help write it,
> but I would be quite surprised if that wasn't easy to do for someone
> with a minimal knowledge of the
Hi,
in my previous mail, I asked if that test was worth anything.
It's possible to know what packages trigger the test:
https://lintian.debian.org/tags/incomplete-creative-commons-license.html
I had a look from the start of the list (took the 20 first), and found
only 4 where I would say it's
4 matches
Mail list logo
