Listening to Lintian while packing a mod_perl module

[Gunnar Wolf <gwolf@gwolf.cx>]

Hi,

Per request of its current maintainer (Cc: of this mail goes to him), I
am working on a NMU of libapache-request-perl because of a new upstream
version. I would like to correct a couple of Lintian warnings in the
process as well. I stumbled across this, however:

W: libapache-request-perl: package-installs-nonbinary-perl-in-usr-lib-perl5 usr/lib/perl5/Apache/libapreq.pm
N:
N:   Architecture-independent Perl code should be placed in
N:   /usr/share/perl5, not /usr/lib/perl5.
N:
W: libapache-request-perl: package-installs-nonbinary-perl-in-usr-lib-perl5 usr/lib/perl5/Apache/Request.pm
W: libapache-request-perl: package-installs-nonbinary-perl-in-usr-lib-perl5 usr/lib/perl5/Apache/Cookie.pm

Now, I started digging a bit into this - Out of 752 files I have in my
/usr/lib/perl5, 121 are plain Perl modules - Quite a sizable proportion!
Is this policy requirement enforceable at all? Could lintian be raising
a false positive warning?

I checked also the module's auto-generated Makefile - It does have this:

PERL_LIB = /usr/share/perl/5.8.0
PERL_ARCHLIB = /usr/lib/perl/5.8.0

So... I understand that it decides the reported modules are not
architecture-independent.

I like my packages to be lintian-clean - What should I do about this?

Greetings,

-- 
Gunnar Wolf - gwolf@gwolf.cx - (+52-55)5630-9700 ext. 1366
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973  F800 D80E F35A 8BB5 27AF