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

[email protected] (Jonas Smedegaard) Mon, 30 Aug 2021 10:49:16 +0200

Newsgroups	perl.cpan.testers.discuss
Message-ID	<[email protected]>

Quoting David Cantrell (2021-08-29 20:43:52)
> On 29/08/2021 17:34, Slaven Rezic wrote:
> > 17. 08. 2021. u 13:59, Jonas Smedegaard piše:
> >> 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?

> > could be something similar like 
> > https://rt.cpan.org/Ticket/Display.html?id=132139

Thanks, Slaven - and sorry for totally missing your previous bugreport 
addressing this very issue :-/


> 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.

Thanks, David - I was unaware that path-less shebang was treated 
specially.  Using that looks like the most elegant approach.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc (application/pgp-signature, 833 B)