From owner-freebsd-questions@FreeBSD.ORG Wed Mar 24 04:53:22 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 816E716A4CE for ; Wed, 24 Mar 2004 04:53:22 -0800 (PST) Received: from destiny.chrononomicon.com (mail.chrononomicon.com [65.193.73.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2B0F43D39 for ; Wed, 24 Mar 2004 04:53:21 -0800 (PST) (envelope-from bsilver@chrononomicon.com) Received: from [IPv6:::1] (destiny.chrononomicon.com [192.168.1.42]) by destiny.chrononomicon.com (Postfix) with ESMTP id AB5671FDFF for ; Wed, 24 Mar 2004 07:53:09 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v613) In-Reply-To: <4060E747.2050208@mac.com> References: <4060DB5B.20305@mykitchentable.net> <4060E747.2050208@mac.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <37EF4C48-7D92-11D8-8CE1-000A956D2452@chrononomicon.com> Content-Transfer-Encoding: 7bit From: Bart Silverstrim Date: Wed, 24 Mar 2004 07:53:16 -0500 To: FreeBSD Questions X-Mailer: Apple Mail (2.613) Subject: Re: How To Upgrade to Perl 5.8 on 4.9 System? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Mar 2004 12:53:22 -0000 On Mar 23, 2004, at 8:41 PM, Chuck Swiger wrote: > Drew Tomlinson wrote: >> I'm using 4.9-RELEASE. Is is possible to upgrade Perl from the >> default 5.005 version to 5.8.2? > > Yes. > >> Are there any steps required beyond installing the port? > > Try: > > cd /usr/ports/lang/perl5.8 > make install > use.perl port > I also had to re-install some of my ports after installing the new Perl and switching the system perl to the newer version (4.9-release-p3). Otherwise I saw failures when I restarted Perl applications... Dunno if a reboot would have fixed it, but I noticed that when I did a make deinstall, make clean, then make install of the ports that acted up, part of the messages mentioned the newer version of PERL :-) Just a note in case you run into the problems I did...maybe I did something wrong in the process, but this worked amid the rising feeling of panic :-)