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

Jonathan Swartz swartz at pobox.com
Wed Feb 3 16:01:54 PST 2010

At my latest job, I've started to treat critical vendor software  
(Perl, Apache, and all CPAN modules) the same way as the web code: it  
is all under version control, and it all gets rsynced out to  
production during a release. Still too early to tell whether this is  
overkill. But I do feel highly organized and it's nice not to have to  
worry about which modules are installed where.

On Feb 3, 2010, at 3:50 PM, Bryan Beeley wrote:

> 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.
> _______________________________________________
> SanFrancisco-pm mailing list
> SanFrancisco-pm at pm.org
> http://mail.pm.org/mailman/listinfo/sanfrancisco-pm

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

More information about the SanFrancisco-pm mailing list