From owner-freebsd-stable@FreeBSD.ORG Wed Jul 10 11:01:44 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E1313840 for ; Wed, 10 Jul 2013 11:01:44 +0000 (UTC) (envelope-from fabian@wenks.ch) Received: from batman.home4u.ch (batman.home4u.ch [IPv6:2001:8a8:1005:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 58E1F13BB for ; Wed, 10 Jul 2013 11:01:43 +0000 (UTC) X-Virus-Scanned: amavisd-new at home4u.ch Received: from flashback.wenks.ch (fabian@flashback.wenks.ch [IPv6:2001:8a8:1005:1:223:dfff:fedf:13c9]) (authenticated bits=0) by batman.home4u.ch (8.14.5/8.14.5) with ESMTP id r6AB1fkt035206 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 10 Jul 2013 13:01:41 +0200 (CEST) (envelope-from fabian@wenks.ch) Message-ID: <51DD3F14.9010500@wenks.ch> Date: Wed, 10 Jul 2013 13:01:40 +0200 From: Fabian Wenk User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: perl upgrade woes -- how to best reconcile? References: <51DBEB9F.7020803@wenks.ch> <44f72b29a68d30c276b13ee4a2730cc9.authenticated@ultimatedns.net> In-Reply-To: <44f72b29a68d30c276b13ee4a2730cc9.authenticated@ultimatedns.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 11:01:44 -0000 Hello Chris On 09.07.2013 20:24, Chris H wrote: > Greetings Fabian, and thank you for your reply. You're welcome. > My perl5 tree currently looks like: > /usr/local/lib/perl5/5.12/man/ > man3/ > whatis > /usr/local/lib/perl5/5.12.4/ > man3/ > whatis > What a mess! If only whatis is left below 5.12.4, then you can remove the whole 5.12.4 folder. And also /usr/local/lib/perl5/site_perl/5.12.4/, if it does exist and does not contain anything relevant. > In the end, I guess the moral of the story is; don't upgrade. This is a bad idea, at least from the security point of view. > I've been on BSD since the late 70's, and as such, am no stranger > to the upgrade path. But recent experience seems to show, things > aren't getting any easier (or necessarily better). :( Sure, there are sometimes bumps on the road, but I had never any real show stopper and could always get it to work. I did install my two private servers back in 2007 with 6.x, upgraded to 7.x and just recently from 7.4 to 9.1. For the Ports I always used portupgrade. At least for the Ports it helps if you are doing it regularly, so the steps are not that huge. Important to always check /usr/ports/UPDATING. Currently I do upgrade the Ports around every 4 weeks, and additional when portaudit complains and I decide that I need to do it right now. >> The next big challenge then will be the upgrade to e.g. 5.14.x or >> 5.16.x. > > I don't think I'm even willing to go there, after this mess. As Mark pointed out, ports-mgmt/poudriere together with pkgng (ports-mgmt/pkg) looks promising. Sure something I did put on my todo list. > Thanks again, for taking the time to respond. You're welcome. PS: No need to use "reply all", reply only to the list is perfect, as I do filter e-mails based on the "List-Id" header line. bye Fabian