Automated testing failure

[ben]

So I've got my module listed on cpan, and other folks are downloading
it. Great, but it looks like mostly it's being tested mostly by
automated scripts which is fine, but most of these systems appear to not
have pam headers which is not. what is the best practice for dealing
with binary modules which depend on third party librarys? wget? die? exit 0?

Module.xs:5:33: error: security/_pam_types.h: No such file or directory

see also
http://www.cpantesters.org/cpan/report/01ca4fb6-501e-11e1-92a9-dbd173dd2dbe

thanks,
ben
--
Ben Hildred
Estimator
Applied Plastic Coatings, Inc.
5000 Tabor St.
Wheat Ridge, CO 80033
303 424 9200
F: 303 424 8800
***@appliedplastic.com
http://appliedplastic.com

[Nicholas Clark]

Post by ben
So I've got my module listed on cpan, and other folks are downloading
it. Great, but it looks like mostly it's being tested mostly by
automated scripts which is fine, but most of these systems appear to not
have pam headers which is not. what is the best practice for dealing
with binary modules which depend on third party librarys? wget? die? exit 0?

I think it's exit 0

"How can I stop getting FAIL reports for missing libraries or other
non-Perl dependencies?"

If you have some special dependencies and don't want to get CPAN Testers
reports if a dependency is not available, just exit from the Makefile.PL
or Build.PL normally (with an exit code of 0) before the Makefile or
Build file is created.

exit 0 unless some_dependency_is_met();

http://wiki.cpantesters.org/wiki/CPANAuthorNotes

That section continues with a suggestion that Devel::CheckLib might be
useful in this sort of situation.

Nicholas Clark

[Sisyphus]

----- Original Message -----
From: "ben" <***@appliedplastic.com>
To: <perl-***@perl.org>
Sent: Thursday, February 09, 2012 12:38 PM
Subject: Automated testing failure

Post by ben
what is the best practice for dealing
with binary modules which depend on third party librarys? wget? die? exit 0?

Not sure what the best practice is, but the common practice is to have
Devel::CheckLib handle the checking for the presence of the 3rd party
library.

In the event that the 3rd party library cannot be located I think you want
the 'perl Makefile.pl' process to 'exit 0' - or you could perhaps set things
up so that the 3rd party lib is then fetched via Alien:: , in which case the
build can then go ahead.

Cheers,
Rob