Michael G Schwern schrieb:
On 7/6/06, Steffen Mueller <[EMAIL PROTECTED]> wrote:
Versions of Module::Install < 0.61 do not work on the current ActivePerl
release 5.8.8 build 817.
What's broken and why suddenly 5.8.8?
ActiveState introduced some new form of local configuration or
something. Module::Install couldn't handle it until 0.61. M::I's change
log would have told you:
[Changes for 0.61 - 2006-03-15]
* ActivePerl::Config on case-insensitive filesystems interacts
erroneously with Module::Install's (outdated) @INC hack, so remove it.
(Patch from Gisle Aas)
[...]
Sounds like its a combination of an M::I hack and Windows being the bad
platform its often perceived as.
5.8.8 because AS Perl build 817 *is* 5.8.8. Build 816 was the first
5.8.8 build and a "bad" build (some symbols weren't exported, PAR broke,
etc.) which is why 817 was pushed out of the door quickly. I don't
*think* versions prior to build 816 were affected. Now, that doesn't
help. It just means people who have AS Perl on their boxes since before
the 816 release won't notice a problem. (Hence the cpan testers results
for win32 are likely PASS if no other problems exist.) But if a new Perl
programmer or an end user who wants to run an application written in
Perl on Windows installs AS Perl build 817 (which happens to be 5.8.8),
he or she will not be able to install many modules from CPAN. (One way
or another you'll end up installing a M::I based module due to
dependencies.)
Just one more thing. Please, nobody suggest that people download older
AS Perl releases to fix this. It's not going to happen. Unless, of
course, you want to limit the usage of Perl (and CPAN) to programmers
and sysadmins.
Does that clarify things?
Steffen
