Hello,
Thanks for reporting this! I agree with you and have reviewed my code. Internally the module uses Pod::Find to search for installed Pod files. I'm passing the "-inc" argument to it to enable searching across all possible paths.
sub _known_podfile {
...
my $filename = Pod::Find::pod_where( {
'-inc' => 1,
}, $link );
...
}
If that fails to find a hit my module will then search the cpan for matching files. If I am right, Pod::Find isn't properly searching your @INC or $PERL5LIB? Or is it because of your unique case of "new" module being added? Could you please help me reproduce this so I can better understand what is failing? Thanks!
On Sat Jun 23 12:31:45 2012, ETHER wrote:
Show quoted text> On Sun Sep 11 17:39:24 2011, DROLSKY wrote:
> > If I add a new module do a distro and link to it from my pod, the tests
> > fail.
> >
> > It'd be great if the link checking looked under blib or lib as
> > appropriate and found all the packages that are part of the current
> > distro. Then it could just whitelist them.
>
> It should really look in all of $PERL5LIB, which would handle the
> blib/lib case as well.
--
~Apocalypse
