in reply to Re: Why not a "living" PerlDoc? Others have it, why not Perl?
in thread Why not a "living" PerlDoc? Others have it, why not Perl?
I unpacked it, and built it yesterday. I didn't actually install it into my systems repository. But simply built, and tested it. Then moved it into a relative folder to the web space, and gave it a try.
It didn't work as expected. There appears to be at least one issue with it's call to DBI
I didn't really look into it, and don't really want to address it here (should probably go to SOPW). But I'm guessing it might have something to do with it's age, and possible differences in DBI -- AnnoCPAN::DBI v my system' DBI. Just thought I'd throw out a heads-up, that's all.index.cgi: Use of uninitialized value in lc at /my/path/to/site_perl/D +BI.pm line 196 # path above modified, for brevity
I too, thought about using my local system' Perl for the notes. As to my plans for this implimentation; I had intended to simply dump many, if not all versions of Perl into the CPAN folder, off it's root -- this is the default setup for Modules.
It downloads the repository there. The nice thing is. If you don't download the repository. You simply dump the tar balls into the CPAN folder, and it'll work from/on those. I thought that was a definite plus.
Sadly. Due to the DBI issue. I can't comment regarding the database setups you commented on. :(
Thanks, wjw. For taking the time to respond, and your thoughts on it.
EDIT: occurred to me just now, AnnoCPAN, as it is, mustn't be sending lang/encoding. Which causes DBI (and Perl) to complain.
Beginning to sound like a bit more work. :(
--Chris
#!/usr/bin/perl -Tw use Perl::Always or die; my $perl_version = (5.12.5); print $perl_version;
|
|---|