[tpm] Upgrading Perl on Debian & Derivatives

Olaf Alders olaf at vilerichard.com
Mon Aug 30 11:27:16 PDT 2010

On 2010-08-30, at 2:20 PM, Scott Elcomb wrote:

> On Mon, Aug 30, 2010 at 2:01 PM, Olaf Alders <olaf at vilerichard.com> wrote:
>> On 2010-08-30, at 1:48 PM, Stuart Watt wrote:
>>> If I was you, I'd use the separate Perl. I know that the Debian base Perl is pretty good, but it is installed for a different purpose (to help manage the OS) and cannot be guaranteed to be maintained as you need. It isn't too bad to do this, and most of your modules will probably build OK. If you stick with the OS Perl there is a risk that an OS update breaks something for you, or that you break the OS in some subtle way by upgrading a system module.
>>> I tend to use PATH hacking rather than a link, though, so that perldoc and the cpan command and its friends relate to your Perl rather than the system one. I just tend to regard the OS Perl is best not touched, or even used, when I can help it.
>> I would second this.  I learned the hard way as well on an Ubuntu system.  Now I like to install a local perl and then just add that to my path.  Works quite nicely for me.
> It's the shebang lines in the various scripts that are killing me -
> they all reference /usr/bin/perl.  After working with the CMS (bug
> fixes, feature enhancements etc) I'll need to push things back out to
> the production servers.  (Maybe I should just automate modifications
> to the shebang lines when pulling sources and pushing updates?)

Have you tried /usr/bin/env perl in your shebang?  That might give you a little more flexibility between development and production machines.  Just a thought!

Olaf Alders
olaf at vilerichard.com

http://vilerichard.com -- folk rock

More information about the toronto-pm mailing list