Date: Sat, 12 Mar 2005 17:22:59 +0000 From: Tim Bishop <tim-lists@bishnet.net> To: Adam Weinberger <adamw@FreeBSD.org> Cc: Joe Marcus Clarke <marcus@FreeBSD.org> Subject: Re: Presenting GNOME 2.10 for FreeBSD Message-ID: <20050312172259.GC42687@carrick.bishnet.net> In-Reply-To: <42332468.1050904@FreeBSD.org> References: <1110628437.30113.23.camel@shumai.marcuscom.com> <20050312165444.GA42687@carrick.bishnet.net> <42332468.1050904@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 12, 2005 at 12:18:32PM -0500, Adam Weinberger wrote: > Tim Bishop wrote: > >On Sat, Mar 12, 2005 at 06:53:57AM -0500, Joe Marcus Clarke wrote: > > > >>As always, GNOME users should _not_ use portupgrade alone to upgrade to > >>2.10. Instead, get the gnome_upgrade.sh script from > >>http://www.FreeBSD.org/gnome/gnome_upgrade.sh (note: you may have to > >>wait for the website to sync before the script is updated for 2.10. You > >>can get the latest version at > >>http://www.marcuscom.com/downloads/gnome_upgrade29.sh if you don't want > >>to wait). > > > > > >Not overly impressed so far. The upgrade script (the second link above) > >carefully removed a long list of ports, then failed later on building > >openoffice. I'm now left with a system that's nicely crippled. > > > >I can put it back together - but it doesn't seem that "safe". > > Your system isn't crippled, Tim. In /var/tmp, you have a file named > gnome_upgrade_lst.XXXXX (the X's are random chars). All you have to do > is fix the openoffice build problem -- or remove the openoffice line > from that file, and do: > > gnome_upgrade.sh -restart /var/tmp/gnome_upgrade_lst.XXXXX > > and it will pick up where it left off. Thanks. It depends on your definition of crippled - I can't use it that well as it stands. I'll give what you suggest a go :-) Cheers, Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050312172259.GC42687>