I did not have it on my Linux machines and as I tried to install it, I could not get far. As it seem this module does not exist any more. According to this note the module was made obsolete back in 5.6.0.
My first thought was that the client might be still using some ancient version of Perl (yeah, I know, bad reflexes, but I encountered so many such cases). After some further Google-ing I found this link on ActiveState Env::Array I don't have ActivePerl installed here but I guess that's there in the AP distribution.
This is the first time I encounter a case where there is a module in ActivePerl that is not on CPAN.
Are there more such cases?
Is there something we should do about this?
My immediate issue is of course that I cannot try the
clients code without modification but...
Can we take this (and probably similar) modules from the
ActivePerl distro and upload to CPAN?
Should we?
I wonder if I should discourage the client from using this module so their code won't depend on ActivePerl.
I don't have ActivePerl installed here but I guess that's there in the AP distribution.I have three Win32 ActivePerl versions: 638 (perl-5.6.1), 802 (perl-5.8.0), and 815 (perl-5.8.7), and none have the Env::Array module. Probably the Env::Array documentation is there for the benefit of users of older ActivePerls before the module became obsolete.
Can we take this (and probably similar) modules from the ActivePerl distro and upload to CPAN? Should we?Unless there's an explicit copyright statement accompanying the module, it would probably be a good idea to ask ActiveState about this. As ActivePerl for some time has been built from the standard Perl sources and CPAN modules, probably the only modules in ActivePerl that would be of general interest that aren't already on CPAN are PPM (Programmer's Package Manager, v 3) modules and the ActivePerl DocTools used to build and maintain HTML documentation. However, my understanding is that these particular modules aren't available for distribution outside of ActivePerl.
Well, if you look at the Env::Array docs, you will find it does exactly what the core module Env also does, and as far as I can tell with a quick glance, they have the same interface. I guess Env::Array was simply subsumed into Env at some point.
I dont think theres any general lesson to be taken from this case.
Makeshifts last the longest.
Can we take this (and probably similar) modules from the ActivePerl distro and upload to CPAN? Should we?You'd have to consult with the author. Presumably he had a reason for removing it from CPAN. The module is still available on backpan. (Assuming that's the same module; I guess there's a possibility he removed his CPAN version because of a different module with the same name in ActivePerl.)
--
In Bob We Trust, All Others Bring Data.
In the source for [cpan://Env], I note there is a line that reads:
package Env::Array;
So it would seem that Env::Array is simply part of the Env module.
perlmonks.org content © perlmonks.org and Aristotle, belg4mit, choedebeck, DaWolf, radiantmatrix, randyk, szabgab, ysth
prlmnks.org © 2006 edmund von der burg (eccles & toad)
v 0.03