Re: Maintaining Local CPAN Patches

Suggested improvement. Use CPAN::Mini to create a local copy of CPAN, and then inject your versions of patched modules into it. And then configure all of your machines to get copies of modules they need off of that version of CPAN. And now all automated tools will automatically go against your CPAN server and will not accidentally install the wrong version of the module.

Bonus, when you go to install new machines, you'll know that they are getting versions of CPAN modules that have actually been tested in your development environment. (Just be sure to actually upgrade regularly to avoid the pain of a "big bang" upgrade down the road.)

I forget the exact details of setting this up, but brian_d_foy gave an excellent talk on this late last year to the Los Angeles perlmongers. You should be able to get them from him (possibly for the cost of ordering a back issue of The Perl Journal).

Comment on Re: Maintaining Local CPAN Patches

Replies are listed 'Best First'.
Re^2: Maintaining Local CPAN Patches by chromatic (Archbishop) on Feb 28, 2008 at 00:34 UTC
This is an excellent suggestion, worth more than just an upvote.	[reply]
Re^2: Maintaining Local CPAN Patches by brian_d_foy (Abbot) on Mar 03, 2008 at 18:02 UTC
Perlcast has the audio of my Making My Own CPAN talk from the Los Angeles Perl Mongers, and the slides are on SlideShare as well as on my personal homepage. It was also an article in the Fall 2007 issue of The Perl Review (but that's the same info in the Perlcast audio and the slides). I also gave this at a lightning talk at Frozen Perl (PDF). -- brian d foy <brian@stonehenge.com> Subscribe to The Perl Review	[reply]