From owner-freebsd-ports@FreeBSD.ORG Sat Feb 25 18:14:43 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4175C16A420 for ; Sat, 25 Feb 2006 18:14:43 +0000 (GMT) (envelope-from spadge@fromley.net) Received: from mta09-winn.ispmail.ntl.com (mta09-winn.ispmail.ntl.com [81.103.221.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4A7343D45 for ; Sat, 25 Feb 2006 18:14:41 +0000 (GMT) (envelope-from spadge@fromley.net) Received: from aamta12-winn.ispmail.ntl.com ([81.103.221.35]) by mta09-winn.ispmail.ntl.com with ESMTP id <20060225181440.ZRXA23947.mta09-winn.ispmail.ntl.com@aamta12-winn.ispmail.ntl.com>; Sat, 25 Feb 2006 18:14:40 +0000 Received: from tobermory.home ([82.18.11.31]) by aamta12-winn.ispmail.ntl.com with ESMTP id <20060225181440.UYDZ1804.aamta12-winn.ispmail.ntl.com@tobermory.home>; Sat, 25 Feb 2006 18:14:40 +0000 Received: from [192.168.124.185] (unknown [192.168.124.185]) by tobermory.home (Postfix) with ESMTP id 8E429A6C3D; Sat, 25 Feb 2006 18:14:37 +0000 (GMT) Message-ID: <44009E8C.2080301@fromley.net> Date: Sat, 25 Feb 2006 18:14:36 +0000 From: Spadge User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeremy Messenger References: <44008ED7.6050406@averageadmins.com> <4400917C.4010808@computer.org> <440096E7.1000806@fromley.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jeff Cross , freebsd-ports@freebsd.org, Eric Schuele Subject: Re: Trouble Upgrading Ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2006 18:14:43 -0000 Jeremy Messenger wrote: > > Did you read in the /usr/ports/UPDATING? Yes, I did, thanks. > >> I once wrote a shell script to combat this sort of behaviour, as it >> is something I have run up against time and time again with the perl5 >> port. It looks something like this (I fully expect my email to kill >> the formatting of this, with like linewrap and everything, so beware): > > > We have a tool for that, an answer is in the /usr/ports/UPDATING. > > Cheers, > Mezz "If you want such packages to remain operational, you will have to reinstall then by hand or via portupgrade." Not a bad argument for my script, as that is precisely what it does, albeit indiscriminately. I'm not knocking your work at all, but IIRC I first wrote this script before perl-after-upgrade was included in the package. I got the xargs from UPDATING back when that was the advice given by the ports maintainers. I also feel a bit funny sometimes about running a perl script to fix a broken perl install. Call me superstitious. I'm *not* saying to anyone "don't use perl-after-upgrade". It's great, very useful, and I like it plenty. I am, however, offering up my homemade bash alternative for anyone who would prefer to use something more bashy than perl-after-upgrade. There's a lot of people out there who feel more at home editing a bash shell script than they do working their way through perl script. Thanks for your earlier comments. -- Spadge "Intoccabile" www.fromley.com