Stories
Slash Boxes
Comments
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

use Perl Log In

Log In

[ Create a new account ]

Alias (5735)

Alias
  (email not shown publicly)
http://ali.as/

Journal of Alias (5735)

Tuesday November 06, 2007
09:14 PM

Request for Comments: Strawberry Perl pre-installed modules

[ #34849 ]

I'm one or two test runs away from completing the image-generation elements of the new Perl::Dist implementation.

This means I will be able to do distribution releases in .zip form for people to test (they won't have the .exe or .msi installer).

While I continue onwards to finish the re-implementation of the .exe install generation, I'd like to get some feedback from people on any modules that they would like to come pre-installed with Strawberry Perl.

Up to this point, I've wanted to limit the extra modules in Strawberry to just toolchain modules, and create a separate "Chocolate Perl" that bundles a whole ton of extras.

But feedback from Strawberry users seems to show there's a preferred middle group, with some small set of modules bundled that are otherwise very difficult to install (Expat and libxml are the biggest two requested).

I'd add SQLite to that list, but unfortunately DBD::SQLite is currently broken on Win32 due to a forking (and thus failing) test.

What else would people like to come pre-installed with Strawberry, other than toolchain modules like PAR::Dist.


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Request for Comments: Strawberry Perl pre-installed modules 13 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'd like nothing more than the ones you listed already (Expat and libxml). It is going to be really difficult to pick and choose otherwise because there are quite a few "cool" modules that don't install easily.
  • Definately expat/libxml will make lives easier.

    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.
    • Install Win32 OpenSSL [slproweb.com] and Strawberry Perl will use it just fine. I haven't tried OpenSSH yet.

    • 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 :)

  • 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.

  • Or at least libwin32, which is pretty valuable for building other Win32 apps.

    Also, if including DBD::SQLite, then shouldn't DBI be included ?

  • This thread and my plea to NOT use 1.13/1.14 prompted me to finally file the RT once I re-figured out how to reproduce it.

    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+
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.