Jerry D. Hedden
|| at Feb 12, 2010 at 8:45 pm
With 5.11, the order of @INC has been changed to put 'site_perl' in
the 'front' of the array. This means that for dual-lived modules, the
'core' version is in 'perl', and if it is update from CPAN, the CPAN
version will 'mask it' when it gets installed in 'site_perl'. In this
way, the 'core' stays unperturbed even if modules are updated.
Hence, Makefile.PL (or whatever) needs to have the following construct
for dual-lived modules:
INSTALLDIRS => ((($] >= 5.???) || ($] < 5.011)) ? 'perl' : 'site'),
Where the lower version number is when the module was first introduced
into 'core' (as per Corelist.pm).
On Fri, Feb 12, 2010 at 14:12, Curtis Jewell
On Fri, 12 Feb 2010 12:16 -0600, "Todd Rinaldo" wrote:
A recent discussion has come up in the RT queue for Locale::Codes
concerning what the install destination for dual core modules should be.
If the module is not deprecated, is there any documentation on where CPAN
installed dual core modules are supposed to install to?
My understanding (no particular documentation that I know of - maybe
there should be) is that they install to 'core', not to 'site', unless
deprecated , or they aren't in core yet. (in which case, it's the other
"Your random numbers are not that random" -- perl-5.10.1.tar.gz/util.c
Strawberry Perl for Windows betas: http://strawberryperl.com/beta/