Re: test failed missing POD::Parser despite a dependency of required POD::Constants

On 29/08/2021 17:34, Slaven Rezic wrote:
> 17. 08. 2021. u 13:59, Jonas Smedegaard piše:
>> Hi,
>>
>> I am trying to understand the real cause of the test failure here:
>> http://www.cpantesters.org/cpan/report/9420f4a4-feca-11eb-bc66-57723b537541
>>
>> Error message talks about missing POD::Parser, and yes that module is
>> needed, but should be pulled in since it is a runtime-requirement of
>> POD::Constants which the cpantest states is installed.
>>
>> What am I missing?
>>
> Hi Jonas,
> 
> could be something similar like 
> https://rt.cpan.org/Ticket/Display.html?id=132139

Indeed. bin/licensecheck has `#!/usr/bin/env perl` so it's using 
whichever perl is first in the path, not whichever perl your code is 
being tested with.

Best practice is to instead have `#!perl` as a placeholder shebang line. 
Then when you `make` (using EU::MM) the path to the correct perl will be 
filled in for you, in a copy of the script at blib/script/licensecheck, 
which is what will in turn be installed. Run the version in blib/script 
in your tests and you should be good.

Alternatively you could explicitly invoke your script using the correct 
perl with something like:

     use Config;
     system($Config{perlpath}, 'bin/licensecheck', ...);

-- 
David Cantrell