Re: [mass bug] New license problem/sourceless fil/privacy problems detected by lintian
- To: firstname.lastname@example.org
- Subject: Re: [mass bug] New license problem/sourceless fil/privacy problems detected by lintian
- From: Julian Taylor <email@example.com>
- Date: Thu, 16 Jan 2014 20:18:38 +0100
- Message-id: <52D8308E.firstname.lastname@example.org>
- In-reply-to: <CAK0OdpxETE1U11zEQu6sBfxXhmygYT9GYpu4a+NvzkRsMHo=UA@mail.gmail.com>
- References: <CAE2SPAauKJQwx_T2+B9GTX=tgiQPvNP0_+LD4r0yB0TFsC1JOw@mail.gmail.com> <CAK0OdpxETE1U11zEQu6sBfxXhmygYT9GYpu4a+NvzkRsMHo=UA@mail.gmail.com>
On 16.01.2014 19:37, Bálint Réczey wrote:
> Hi Bastien,
> 2014/1/15 Bastien ROUCARIES <email@example.com>:
>> I am slowly manually checking if source is present and fill bug when
>> (line too long some comments) in newer lintian version.
a useful heuristic to reduce false positives here would be to check if
there is a bigger file with the same name but without the ".min"
extension next to it.
Most of my upstreams ship both compressed files for users and
uncompressed files for packagers.
Possibly also the presence of a minifier in the build depends (lessc,
uglifyjs, yui-compressor) could be used.
What is the severity of the only-minified source bugs you intend to file?
Will it be treated differently if the file without source is not used in
the binary package? (E.g. packaged jquery is used instead)