Well, yeah. It brings you to the directory for the source, which contains the POD as text in a README file. Once they appear on CPAN, you can just use CPAN to read the docs in a nicer format.
Oh. Fixing... update: fixed.
Let this be a lesson to you:
for my (grep -d, glob "*") {
(my $mod = $_) =~ s/-/::/g;
my ($latest) = sort { $b <=> $a } map /.*-(\d+\.?\d*)/, glob "$_/*";
my $what = "";
open README, "< $_/$_-$latest/README";
while (<README>) { # AGH! THIS KILLED MY OLD $_
($what) = /$mod - (.*)/ and last;
}
close README;
print "<h2><tt>$mod $latest</tt></h2>\n";
print "<b>\u$what</b>\n";
print "<ul><li><a href='$_/$_-$latest/'>Documentation</a> and source
+\n";
print "<li><a href='$_/$_-$latest.tar.gz'>Download</a></ul>\n";
}
If you follow that code carefully, you'll see why the links were messed up. When I read from README, I was setting $_ each time, which clobbered the $_ that held the filename.
_____________________________________________________
Jeff [japhy]Pinyan:
Perl,
regex,
and perl
hacker, who'd like a job (NYC-area)
s++=END;++y(;-P)}y js++=;shajsj<++y(p-q)}?print:??;
| [reply]
[d/l] |