From owner-freebsd-ports@FreeBSD.ORG Tue Jun 1 18:26:10 2004 Return-Path: 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 C7A6A16A4CF for ; Tue, 1 Jun 2004 18:26:10 -0700 (PDT) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8063C43D5F for ; Tue, 1 Jun 2004 18:26:10 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.1] (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id 79C4DBB; Tue, 1 Jun 2004 21:26:08 -0400 (EDT) From: "Brandon S. Allbery KF8NH" To: Jeremy Messenger In-Reply-To: References: <20040602010715.GA96875@prophecy.dyndns.org> Content-Type: text/plain Message-Id: <1086139566.21900.7.camel@rushlight.kf8nh.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 01 Jun 2004 21:26:07 -0400 Content-Transfer-Encoding: 7bit cc: FreeBSD Ports List cc: Christopher Nehren Subject: Re: Perl voodoo in ports/UPDATING X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 01:26:10 -0000 On Tue, 2004-06-01 at 21:16, Jeremy Messenger wrote: > On Tue, 1 Jun 2004 21:07:15 -0400, Christopher Nehren > wrote: > > > In regard to the new Perl version, ports/UPDATING has of course been > > changed with some instructions on how to proceed. It includes some real > > voodoo which really shows the beauty of Unix. But wouldn't 'portupgrade > > -rf perl\*5.8.4' be much simpler? And if the user has a threaded Perl > > installed, the command listed in UPDATING won't work. > > Before the perl was added in UPDATING, I did the 'portupgrade -f p5-\*' > and it seems work fine. No problem to run GNOME, portlint, tinderbox, perl > gtk2 and etc so far. Maybe, there is some apps that need to be rebuild > that I don't have them installed. Most stuff that depends on perl doesn't link libperl.so into itself, so for the most part it's not necessary to rebuild them when upgrading perl. (An exception is eperl, but last I checked it wouldn't build against 5.8.x anyway. Another class of exceptions is ports which install related perl modules along with themselves; I don't know if any of the FreeBSD ports do so, but the stock ImageMagick and pilot-link distributions are examples of this.) However, whenever upgrading perl to a new version (as opposed to a new release of an existing version), *all* modules need to be rebuilt; I typically upgrade perl manually, "use.perl port", and "portupgrade -f p5-\*" to handle this. (I considered making it a postinstall rule for perl, but I don't know if it's safe to call portupgrade from within a postinstall rule in pkgtools.conf.) I suspect there isn't a clean way to tell the ports system about this kind of relationship. -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH