[sf-perl] What version of perl and what OS do you use? [poll]

[Bryan Beeley]

We do something similar.  We compile everything on a single tree then 
rsync it to all our servers.  We usually add modules to our production 
servers as soon as we start using them in development, just to make sure 
we aren't out of sync when we push out the next code release.

Bryan

David Alban wrote:
> tangentially related to your question...
>
> i do tools for (mostly) the release engineering group at work.  my
> company is a java shop, so not too many of us use perl.  rather than
> getting sysadmins to install new modules when i need one, i decided a
> while back to keep all of our tools / libraries / etc in a single tree
> on our nas (which is mounted to all the machines which matter).  so
> all folks have to do to use our tools is to mount that nas partition.
>
> home grown modules go under </nas/reg/lib/perl5/>.  cpan modules that
> i need go there, too.  (reg is an acronym which stands for release
> engineering group.)  so any programs that want to use these modules
> include the use statement:
>
>   use lib '/nas/reg/lib/perl';
>
> (/nas/reg/lib/perl is a symlink to /nas/reg/lib/perl5)
>
> what i like is that i can maintain the contents in / updates to our
> nas partition.
>
> On Wed, Feb 3, 2010 at 3:11 PM, Earl Ruby <eruby at knowledgematters.net> wrote:
>   
>> I'm also interested to know how people manage Perl in their production
>> environments, that is, how you make sure that all of the CPAN modules
>> you need are installed and how you verify that all production servers
>> are using the same module versions. I usually build modules on a dev
>> server, then use cpan2rpm to create RPMs, then install from the RPM
>> files in production.
>>     
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/sanfrancisco-pm/attachments/20100203/0c479286/attachment-0001.html>