in reply to graceful handling of perl upgrades on server?

But is there some simpler/easier/graceful/automagic way to approach this?

My procedure is to never use the system perl for my applications. It is extremely easy to build a seperate perl, and it avoids an entire class of problems like the one you describe.

See Re: 2nd Perl installation on Mac OSX for how and blaming perl for not using a build policy for why.

  • Comment on Re: graceful handling of perl upgrades on server?