From owner-freebsd-questions@FreeBSD.ORG Thu Jul 7 20:14:33 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 BB0F016A41C for ; Thu, 7 Jul 2005 20:14:33 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73BD743D49 for ; Thu, 7 Jul 2005 20:14:33 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 15C85CBAFCE for ; Thu, 7 Jul 2005 16:14:32 -0400 (EDT) X-Sasl-enc: IviKToI77laT4y4mheb8Rr4IeiR5tf6GiCKXeJ+TTylL 1120767272 Received: from gumby.localdomain (dsl-80-41-73-249.access.as9105.com [80.41.73.249]) by frontend3.messagingengine.com (Postfix) with ESMTP id 0FB461DC for ; Thu, 7 Jul 2005 16:14:32 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Thu, 7 Jul 2005 21:14:31 +0100 User-Agent: KMail/1.8.1 References: <20050706191003.GA79388@kongemord.krig.net> In-Reply-To: <20050706191003.GA79388@kongemord.krig.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507072114.31582.list-freebsd-2004@morbius.sent.com> Subject: Re: perl-after-upgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2005 20:14:33 -0000 On Wednesday 06 July 2005 20:10, Bob Hall wrote: > I don't know squat about perl. I recently ran portupgrade, which > upgraded perl. Goose stopped working, because the location for Curses.pm > was no longer in @INC. I tried to run perl-after-upgrade, but I couldn't > get it to run. I've got a book that said to use > # perl perl-after-upgrade > or > # ./perl-after-upgrade > I also tried just > # perl-after-upgrade > No joy. Just for the heck of it, I tried > * sh perl-after-upgrade > and dang if it didn't run. It didn't look to me like an sh script, but > what do I know? It wasn't supposed to change anything without the -f > option, but goose ran afterward, so it obviously changed things. I > looked for Curses.pm, and it moved to a directory listed in @INC. > > Anybody have any advice? Comments? How was I supposed to get > perl-after-upgrade to run? I used to be a bit sceptical about portmanager, but for the sake of a few hours of unattended extra building, you can simply ignore this kind of thing.