[sf-perl] running multiple perl versions

Tatsuhiko Miyagawa miyagawa at gmail.com
Mon Feb 22 16:16:46 PST 2010

On Mon, Feb 22, 2010 at 4:12 PM, Chris Weyl <cweyl at alumni.drew.edu> wrote:
> Since regaining what was left of my sanity, I've pretty much given up
> on that approach: I tend to install "our" perl into /opt/perl and then
> manage the installation via git.  It allows for easier testing of code
> w/updates from the CPAN, as well as making deployment easier ("git
> pull; git co new-production" against a bunch of s390x boxen, for
> instance).  It "feels" a little messier, but it does the job quite
> well with a minimum of fuss -- and an easy, known backout plan if
> Something Bad happens.

cpanminus has plugins branch on git and I have 'git_site_perl' plugin
to exactly do this: whenever you install a new module using cpanminus,
your site_perl (local::lib configured path or $Config{installsitelib})
files will be committed to git for versioning.

This is a rip off of nothingmuch's git-site-perl hook and actually
works well with local::lib while his doesn't.

Tatsuhiko Miyagawa

More information about the SanFrancisco-pm mailing list