Hi Niels,
> Does this still trigger if people install it into
> "/usr/include/$MA_DIR/util.h"?
Ah, of course, that's probably why the original implementation was
like that. :)
Fixed here:
https://salsa.debian.org/lintian/lintian/commit/13414ae9a8a366a732bb38c54714bc5f04c25fb5
Regards,
Chris Lamb:
> tags 899192 + pending
> thanks
>
> Russ,
>
>> E: libmutter-2-dev: header-has-overly-generic-name
>> usr/include/mutter/meta/util.h
>>
>> I think this should only trigger on usr/include/util.h specifically, not
>> if the file is in any subdirectory. Generic header names are only a
Chris Lamb writes:
> Russ,
>> E: libmutter-2-dev: header-has-overly-generic-name
>> usr/include/mutter/meta/util.h
>>
>> I think this should only trigger on usr/include/util.h specifically, not
>> if the file is in any subdirectory. Generic header names are only a
>> problem at the top level
tags 899192 + pending
thanks
Russ,
> E: libmutter-2-dev: header-has-overly-generic-name
> usr/include/mutter/meta/util.h
>
> I think this should only trigger on usr/include/util.h specifically, not
> if the file is in any subdirectory. Generic header names are only a
> problem at the top leve
Simon McVittie writes:
> The new check for header-has-overly-generic-name seems too sensitive:
>> E: libmutter-2-dev: header-has-overly-generic-name
>> usr/include/mutter/meta/util.h
> This one is canonically included as while compiling with
> `pkg-config --cflags libmutter-2`, which is just
Package: lintian
Version: 2.5.87
Severity: normal
The new check for header-has-overly-generic-name seems too sensitive:
> E: libmutter-2-dev: header-has-overly-generic-name
> usr/include/mutter/meta/util.h
This one is canonically included as while compiling with
`pkg-config --cflags libmutter-
6 matches
Mail list logo
