Ken Williams wrote:
When we do fix_shebang_line(), we actually write a new svnnotify.new
file, then move the old svnnotify to svnnotify.bak, move svnnotify.new
to svnnotify, and finally delete svnnotify.bak. That should update the
timestamp on svnnotify to the current time, shouldn't it?
After another couple of exchanges with David Wheeler, he finally hit me
upside the head with the real answer:
1) My Perl 5.8.7 installation is provided by SuSE, so it lives in
/usr/bin/perl and /usr/lib/perl5;
2) My custom installed 5.005_05 and 5.6.2 installations live in
/usr/local/bin/perl5... and /usr/local/lib/perl5/...;
3) My $PATH has /usr/local/bin preceed /usr/bin (not uncommon).
So the version of svnnotify that was installed in /usr/local/bin (with
the specialized shebang line) was shadowing the true svnnotify in
/usr/bin. Building would use the correct Perl libraries, but testing
would fail because the svnnotify that was found was the 5.6.2 version
and not the 5.8.7 version.
At this point, all Module::Build could do for me was to warn that there
was another executable script in a different system path that may
prevent the newly installed script from working. I know, patches
welcome... ;-)
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
