NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Nothing More (Score:2)
Amen. (Score:1)
As far as DBD::SQLite is concerned, even if there wasn't a test failure, I vote for not including 1.13/1.14. There's a nasty PK bug in those (Yes damnit, I keep not filing an RT for this) on win32.
Re: (Score:1)
Re: (Score:1)
more external libraries (Score:1)
Re: (Score:2)
Re: (Score:1)
Re: (Score:2)
Re: (Score:1)
Unfortunately, their installer requires Administrator privileges, which is bad as it prevents you from being able to copy the Perl directory around. The DLLs should go into the same directory as perl.exe so they are always around... Also, it would be nice if even Strawberry Perl was of the "Batteries Included" kind, and not only Chocolate :)
Request for Comments: Strawberry Perl pre-installe (Score:1)
I'd like SQLite to be in the distribution (and DBI), but if there's something other than a failing fork() test, skip it.
Another thing that would be really nice to have is SSL support via Crypt::SSLeay [cpan.org] out of the box, but I'm not sure if LWP is on your list. Maybe that's more chocolatey. I hope I can give you a "distro-builder" that downloads the "current" OpenSSL binaries (that is, DLL) and puts them in the right place on Windows, so rebuilding the distribution gets less painful.
Re:Request for Comments: Strawberry Perl pre-insta (Score:1)
LWP is part of the upgrades for the toolchain, so adding SSLeay to that is problem a good idea.
The items on the win32 wiki Misc list ? (Score:1)
Also, if including DBD::SQLite, then shouldn't DBI be included ?
DBD::SQLite Bug (Score:1)
http://rt.cpan.org//Ticket/Display.html?id=30558 [cpan.org]
It's a pretty nasty one, and the only reason I ever caught it was some PK violation tests in Handel, where the subsequent tests after the PK violation tests were also failing under 1.13+