[Pkg-clamav-devel] Add source:Version minimum version requirements for freshclam to clamav, clamav-daemon, and clamav-milter

[Andreas Cadhalpun]

On 04.08.2014 21:00, Sebastian Andrzej Siewior wrote:
> On 2014-07-27 23:27:57 [+0200], Andreas Cadhalpun wrote:
>> OK, I changed that now.
>>
>> When running lintian over the resulting binaries, I noticed some new errors:
>> N: Processing binary package libclamav-dev (version 0.98.4+dfsg-3, arch
>> amd64) ...
>> E: libclamav-dev: pkg-config-bad-directive usr/lib/pkgconfig/libclamav.pc -g
>> E: libclamav-dev: pkg-config-bad-directive usr/lib/pkgconfig/libclamav.pc
>> -fstack-protector
>> E: libclamav-dev: pkg-config-bad-directive usr/lib/pkgconfig/libclamav.pc
>> -O2
>> E: libclamav-dev: pkg-config-bad-directive usr/lib/pkgconfig/libclamav.pc
>> --param=ssp-buffer-size=4
>> E: libclamav-dev: pkg-config-bad-directive usr/lib/pkgconfig/libclamav.pc
>> -Wall
>>
>> It seems that the libclamav.pc.in has an unnecessary @CFLAGS@ in the CFlags
>> row, but I'm not sure if it is really safe to just remove it.
>> What do you think?
>
> This seems to be introduced in latest lintian since it jumps from 0 to
> approx 100 hits since the new version tag.

Yes, I have seen it in the changelog:
  + Added:
[...]
        - pkg-config-bad-directive

> Looking at the CFLAGS, it should be completly harmless to drop those
> you (or lintian) enumerated. I mean if you plan to compile your
> package with -Os and libclamav just gives you -O2 you might just go wtf
> :) The same goes for the other flags

Yes, these flags shouldn't be in the pkg-config file, so I removed them 
now. I also removed the @LIBCLAMAV_LIBS@ from Libs, because I'm pretty 
sure they are also unnecessary, as the libclamav.h header doesn't use 
functionality from these libs (-lz -lbz2).

Best regards,
Andreas