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.
Re:Strawberry Perl
roho on 2007-11-08T09:18:22
I second the request for Devel:ptkdb. It would also be helpful to have the Sybperl modules (Sybase::DBlib and Sybase::CTlib).Re:Strawberry Perl
persicom on 2007-11-09T01:55:41
Sybase, being a commerical product, may not provide a free version of client libs bundle and link in. I think that the DBs could be provided in "Sprinkles" perl, or some other add-on.Re:Strawberry Perl
Alias on 2007-11-08T12:30:47
Unfortunately, I think GUI toolkits are probably where I will draw the line.
That sort of stuff should go into Chocolate Perl.
Re:Strawberry Perl
persicom on 2007-11-09T02:00:07
But given the way the Strawberry is built and installed, TK and Devel::ptkdb should be as simple as
for (qw (Tk Devel::ptkdb)) { get_from_cpan($_); unpack($_); perl_maketestinstall($_); }
Yes?Re:Strawberry Perl
Alias on 2007-11-09T02:18:08
If it's that easy, then there's no need to pre-install it.
The goal here is not to pre-install for pre-install sake.
The goal is to install things that CAN'T be easily installed via CPAN normally, and require non-CPAN installation or configuration.
By providing THOSE things pre-bundled, it makes installation of the CPAN modules much easier.Re:Strawberry Perl
persicom on 2007-11-09T03:05:43
Sorry, I wasn't complete in my post. I was trying to B that it would be that easy to add after the fact. As long as the magic four-step-sequence works (which it should since you are bundling the toolchain, yes?) then I agree that Tk/Devel::ptkdb should live outside of Strawberry proper.
Perhaps GUI extentions be bundled into a release called Fudge.:-) Re:Strawberry Perl
Aristotle on 2007-11-09T05:44:54
And what would the packager for that release be called…?
Re:Strawberry Perl
Alias on 2007-11-10T11:37:45
The mythical Chocolate Perl will indeed come with WxWindows and Tk and a GUI CPAN client and a GUI POD reader, and all sorts of wonderful blue sky stuff.
Of course, it will probably be several hundred meg, but then that's the general idea.
Re:XML::LibXML
Alias on 2007-11-09T02:18:58
Looking at the dependency trees below both XML::Parser and XML::LibXML it would appear that I'll need to pre-install both of them.
