Yes, you can get these on CPAN for 5.8.8, but for @jobs that insist on only using core modules
I have encountered @jobs with just that restriction. Any libre/open software that is not explicitly indemnified by the vendor must be individually approved (along with any dependencies) for the specific version and license.
Perl itself may be an approved product, but non-core modules must go through the same process as any other non-vendor provided resource. Perl 5.10 will not change that aspect of those @jobs, but getting the 5.10 release of Perl approved will be easier than the multitude of individual module updates.
| [reply]
[d/l]
[select] |
Could you have, like, approved Debian etch, and then install all the perl modules from deb packages?
| [reply] |
Only if Debian or SPI can satisfactorily convince the legal department that they can indemnify the company in the event of a lawsuit claiming that protected IP made its way into $MODULE. Otherwise, $company may approve a specific Debian release, but any updates would need a renewed approval.
Some @BigLinuxVendors provide this indemnification, or at least enough of it to keep the lawyers happy.
Also, not all companies are 100% Linux in the datacenter. The Perl provided by @BigUNIXVendors is automatically approved. If they also approve Perl 5.10, then its core modules are also approved. Individual module additions or updates will require explicit approval in many cases.
Sure, it sounds like a Brazil-esque nightmare of bureaucracy; but the rationale is the continued well-being of the company and -- by proxy -- the continued employment of the staff. Big money attracts lawsuits, and many companies would rather go about their business than fight the next SCO.
So, back to the topic, some may want to use Perl 5.10 because it is the easiest way to get Nifty::New::Modules.
| [reply] |