http://qs321.pair.com?node_id=677820


in reply to Testing for non-perl system requirements

The CPAN Testers Wiki has a couple of suggestions related to this under the entry "How can I stop getting FAIL reports for missing libraries or other non-Perl dependencies?".
  • Comment on Re: Testing for non-perl system requirements

Replies are listed 'Best First'.
Re^2: Testing for non-perl system requirements
by leocharre (Priest) on Apr 02, 2008 at 16:35 UTC
    There are some great notes there.
    Nice solutions for OS requirements also.

    It seems that if something is missing, you should exit in the Makefile.PL, that's what Devel::CheckLib suggests.

    Some of it seems bulky, like checking os.. the use-devel-assertos script is iffy, but dammit it works.

    Thank you so much, this is incredibly helpful.

    It seems you can basically test these things in the Makefile.PL. If something is missing, you should warn and exit. There is a convention for bailing out on bad os, 'OS UNSUPPORTED' or 'No support for OS'- I'm trying to find out what the warning should be for a missing binary dependency, or lib, etc- per CPAN tester standards.

    But my main question is answered, the tests should check the distributed code, not the system setup. The Makefile.PL should make decisions such as missing files, etc.. and should not die but exit with warnings if so.

[reply]
      If you've got any suggestions for how to improve the use-devel-assertos and use-devel-checklib scripts then do please let me know, either by email or by filing a ticket in RT.
[reply]

In Section Seekers of Perl Wisdom