From owner-freebsd-questions Wed Aug 14 0:54: 2 2002 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 8195237B401; Wed, 14 Aug 2002 00:53:56 -0700 (PDT) Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0018943E70; Wed, 14 Aug 2002 00:53:53 -0700 (PDT) (envelope-from pjklist@ekahuna.com) Received: from pc-17 (dyn205.ekahuna.com [198.144.200.205]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com; Wed, 14 Aug 2002 00:53:52 -0700 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: questions@FreeBSD.ORG Date: Wed, 14 Aug 2002 00:53:51 -0700 MIME-Version: 1.0 Subject: Re: Ruby-optparst + portupgrade Reply-To: pjklist@ekahuna.com Cc: Kevin Golding , ports@freebsd.org In-reply-to: References: X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Message-ID: <20020814075352814.AAA342@empty1.ekahuna.com@dyn205.ekahuna.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 12 Aug 2002 at 20:24, Kevin Golding boldly uttered: > Someone, quite probably Scott Gerhardt, once wrote: > >My portupgrade et.al. Does not work with the following error: > > > >/usr/local/sbin/portupgrade:34:in `require': No such file to load -- > >optparse (LoadError) > > from /usr/local/sbin/portupgrade:34 > > >I though reinstalling ruby-optparse would fix the problem but ruby-optparse > >does not seem to be in the ports tree anymore, what happened to it? > > It got integrated into ruby-shim. > > Probably best to just pkg_delete portupgrade and install a more recent > version that uses shim instead. > > Kevin I have found in the vast majority of cases that trying to upgrade portupgrade (ie "portupgrade -R portupgrade") causes more problems than it solves.. dependency issues and other failures. Now I typically just remove portupgrade and reinstall whenever it gets out of date, sometimes removing the Ruby modules as well. (so the latest ones get installed when I reinstall portupgrade) Luckily I don't have any other ports/packages that depend on Ruby on any of the boxes I manage. -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message