buildtoc should use the correct path when looking for a .pm's .pod file.
authorNicholas Clark <nick@ccl4.org>
Sat, 17 Dec 2011 20:45:14 +0000 (21:45 +0100)
committerNicholas Clark <nick@ccl4.org>
Mon, 19 Dec 2011 12:55:18 +0000 (13:55 +0100)
commitb186d677a9fa494035b07d613cfd0fdbaf1aaa5d
treeca96f196d80f70a912fff7a4b5d314e85085444a
parentfcdc6846043a49b06ba005ecfc5e9064e17f049d
buildtoc should use the correct path when looking for a .pm's .pod file.

This corrects commit be6d62867c9b925b, which attempted to avoid a warning
about lack of Pod in a .pm file if it had a corresponding .pod file.
However, the commit would never actually find the .pod file because it used
$File::Find::name as the basis for the search, instead of $_. This falls
foul of the same problem as described in the previous commit -
File::Find::find() changes directory, hence $File::Find::name points
somewhere bogus, whilst $_ contains the name to use.

With this change, pod/buildtoc no longer warns about the 20 relevant files.
pod/buildtoc