I browsed the CPAN a bit, but wasn't too happy with the choices there, aside from the fact that any module installs would pretty much defeat the purpose here.
Why is that? That is the point of modules.
Well, as I said we're talking about 32 servers running at least 4 different operating systems here, and we're not comparing versions yet. How many versions of Perl do you think that adds up to? If we're going to install modules under those conditions why not just check the OS version and shell out? I bet there are less combinations that way.
This a professional server environment, with real world serving concerns like big uptime, system restores, etc. The way the sys admins keep on top of all that is to stay as in control of those machines as humanly possible. That means they think long and hard before adding more software dependancies. If they add even one module, that means they've practically doubled the work of all future Perl upgrades (one install to two, plus testing). If they add 10 modules across 32 servers, well that's getting crazy pretty fast.
Don't get me wrong. I love the CPAN and the tons of modules it offers. I'm sure they do too, under the right circumstance. They've got a job to do though and sometimes that makes for hard choices.
James
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
