<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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.<div><br><div><div>On Feb 3, 2010, at 3:50 PM, Bryan Beeley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <div bgcolor="#ffffff" text="#000000"> 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.<br> <br> Bryan<br> <br> David Alban wrote: <blockquote cite="mid:firstname.lastname@example.org" type="cite"> <pre wrap="">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
On Wed, Feb 3, 2010 at 3:11 PM, Earl Ruby <a class="moz-txt-link-rfc2396E" href="mailto:email@example.com"><firstname.lastname@example.org></a> wrote:
</pre> <blockquote type="cite"> <pre wrap="">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.
</pre> </blockquote> <pre wrap=""><!---->
</pre> </blockquote> <br> </div> _______________________________________________<br>SanFrancisco-pm mailing list<br><a href="mailto:SanFranciscoemail@example.com">SanFranciscofirstname.lastname@example.org</a><br>http://mail.pm.org/mailman/listinfo/sanfrancisco-pm<br></blockquote></div><br></div></body></html>