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
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Strawberry also breaks this (Score:1)
It's worth nothing that, at the moment, Strawberry does this all wrong.
The bundled modules we add to the default install go into site.
We're hoping to fix this for the October release, with the Strawberry-bundled extras (and dual-life updates) going into vendor instead of site.
Less breakage in Strawberry in July, hopefully. (Score:1)
I'll speak up and mention what is being done with the MSI (July) builds, which is subtly different, and hopefully closer to right.
The rule I used is: Module::CoreList is checked and what is updating core at installation build time is installed in core and what isn't is installed in site. Some of the dual-lifes do not do this on their own.
And yes, October 2009 will have the ability to use "INSTALLDIRS=vendor". Code has already started to be written. We're already making one horribly big change in July (whic
The new Strawberry Perl for Windows has been released! Check http://strawberryperl.com for it.