Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Dec 2002 23:01:19 -0800
From:      Kent Stewart <kstewart@owt.com>
To:        Roger Merritt <mcrogerm@stjohn.ac.th>, freebsd-questions@FreeBSD.ORG
Subject:   Re: Upgrading the Portupgrade port
Message-ID:  <200212302301.19580.kstewart@owt.com>
In-Reply-To: <5.2.0.9.0.20021231120143.00a02660@127.0.0.1>
References:  <20021226113141988.AAA328@empty1.ekahuna.com@dyn205.ekahuna.com> <5.2.0.9.0.20021231120143.00a02660@127.0.0.1>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Monday 30 December 2002 09:03 pm, Roger Merritt wrote:
> At 02:56 AM 12/27/02, you wrote:
> >On Thursday 26 December 2002 03:35 am, Philip J. Koenig wrote:
> > > Once upon a time it was said that one of the cool things about
> > > Portupgrade, was that you could use it to upgrade itself.
> > > ("portupgrade -{|r|R} portupgrade")
> > >
> > > But this never worked for me - caused all sorts of weird Ruby and
> > > dependency problems, orphaned Ruby shim thingies, etc.
> > >
> > > So I got into the habit of completely removing Portupgrade and
> > > everything associated with it including all the Ruby stuff, and
> > > reinstalling them all, in order to upgrade. (it was the only way
> > > that worked for me)
> > >
> > > Have things improved in the meantime?  Is there an easy way to
> > > upgrade Portupgrade without removing everything and
> > > re-installing?  I currently have the 20020706 version installed.
> >
> >You version is so far back that the upgrade is hopeless. You have
> > things that no long exist as parts of portupgrade and your version
> > can't deal with that. It is easier if you delete the portupgrade,
> > ruby-*, pkg_tartup, and what ever is left and reinstall it.
> >
> >FWIW, it works flawlessly now. I just recently upgraded to the 1216
> >version by using "portupgrade -rpuf ruby".
>
> Just out of curiosity, wouldn't 'portupgrade -rR portupgrade' work as
> well?

Ruby was the base element that had changed and you only needed to build=20
ports that depended on it. There could have been ports others than=20
portupgrade that used ruby.=20

I don't see any dependancy on portupgrade and the "-r" would have been=20
meaningless and from experience "-R" wouldn't have followed chains=20
using ruby.=20

Kent

--=20
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?200212302301.19580.kstewart>