Bug#921080: lintian: warn about non-regenerated Parse::Yapp parsers

2019-02-01 Thread Chris Lamb
Hi Andrius, > > * What if the original code is actually included? How would > >Lintian find that? > > I would expect %.pm to be generated from %.yp, but not necessarily. How reliable is this? Naturally, pre-generated parsers should be regenerated during package build but we can't determin

Bug#921080: lintian: warn about non-regenerated Parse::Yapp parsers

2019-02-01 Thread Andrius Merkys
Hi Chris, On 2019-02-01 15:47, Chris Lamb wrote: > * Can one do this on a subset of filenames? (.pl?) Yes, it's going to be *.pm (Perl module) files only. > * What if the original code is actually included? How would >Lintian find that? I would expect %.pm to be generated from %.yp, but

Bug#921080: lintian: warn about non-regenerated Parse::Yapp parsers

2019-02-01 Thread Chris Lamb
tags 921080 + moreinfo thanks Hi Andrius, > look though the package source for Parse::Yapp-added headers Two quick questions: * Can one do this on a subset of filenames? (.pl?) * What if the original code is actually included? How would Lintian find that? Regards, -- ,''`.

Bug#921080: lintian: warn about non-regenerated Parse::Yapp parsers

2019-02-01 Thread Andrius Merkys
Package: lintian Severity: wishlist Hello, packages sometimes ship pre-generated Parse::Yapp parsers while in principle they have to be generated from their source (this has already been discussed in debian-perl@ [1]). A simple check would be to look though the package source for Parse::Yapp-a