Date: Sun, 06 Nov 2005 05:27:10 -0600 From: "Edwin L. Culp" <eculp@encontacto.net> To: freebsd-ports@freebsd.org Subject: Re: ANNOUNCE: GNOME 2.12.1 has been merged into the ports tree Message-ID: <20051106052710.jn84zulfeo0k4g84@mail.encontacto.net> In-Reply-To: <1131176568.3960.20.camel@shumai.marcuscom.com> References: <1131176568.3960.20.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Joe Marcus Clarke <marcus@FreeBSD.org>: > Now that the freeze in preparation for FreeBSD 6.0 is over (an excellent > release to be sure), it is my great pleasure (on behalf of the FreeBSD > GNOME Team) to announce the general availability of GNOME 2.12 for > FreeBSD. > > The official release notes for GNOME 2.12 can be found at > http://www.gnome.org/start/2.12/notes/en/. FreeBSD-specific > documentation can be found at http://www.FreeBSD.org/gnome/. The > documentation has been updated, but it will be a little while before the > website rebuilds. > > Upgrading from GNOME 2.10 to 2.12 is tricky. You should NOT use > portupgrade by itself to do this upgrade. Instead, download the > gnome_upgrade script from > http://www.marcuscom.com/downloads/gnome_upgrade212.sh. This script is > a wrapper for portupgrade that contains additional logic to steer clear > of some potential pitfalls with the upgrade. Hello, It is always nice to know what you should have done;) A little late, I'm afraid, but when using the script is being used and the upgrade fails because of a power outage after the ports have been uninstalled and not rebuilt, what is the correct proceedure to follow? I reiniciated the update by reexecuting gnome_upgrade212.sh -f and it seems as though I'm going to loose some ports that were deleted during the first execution. When I realized that was a posiblity, I checked the -h option and saw -restart <list filename> that I should add as an argument and don't know where <list filename> might be or if I should have created it before iniciating the upgrade process. What is the recommended procedure in this case? It looks like this could easily be a 24 hour or longer process on a PIII so in 24 hours anything can happen. thanks, ed > If you're used to > gnome_upgrade from previous releases, a lot has changed in this release. > You should run gnome_upgrade.sh (or gnome_upgrade212.sh) with the -h > flag to get the new usage. > > In keeping with FreeBSD GNOME tradition, we held a splash screen contest > to find a great FreeBSD-specific splash screen for our users. This > release's winner is Dominique Goncalves <dominique.goncalves@gmail.com> > whose winning splash screen was inspired by > http://art.gnome.org/contests/2.12-splash/83. All of our submitters' > work has been integrated into x11/gnomesession, and you can use Franz > Kalmmer's great splashsetter (deskutils/splashsetter) to choose the > splash screen you like best. > > Another important bit of news related to GNOME 2.12 is that we are no > longer supporting this release on FreeBSD 4.X. You must be running > FreeBSD 5.3 or higher to get GNOME 2.12 support. > > Finally, the FreeBSD GNOME team would like to extend a special thanks to > all of our testers, especially those that submitted patches: > > Matthew Luckie <mjl@luckie.org.nz> > ade > sajd on #freebsd-gnome > Caelian on #freebsd-gnome > mnag > Yasuda Keisuke <kysd@po.harenet.ne.jp> > Mark Hobden <markhobden@gmail.com> > Sergey Akifyev <asa@agava.com> > Andreas Kohn > > As always, consult our excellent site at http://www.FreeBSD.org/gnome/ > if you need help. If you can't find the answer you're looking for > there, come on over to #freebsd-gnome on FreeNode, or drop us an email > at freebsd-gnome@FreeBSD.org. Enjoy GNOME 2.12 for FreeBSD. > > Marcus on behalf of the FreeBSD GNOME Team > > -- > Joe Marcus Clarke > FreeBSD GNOME Team :: gnome@FreeBSD.org > FreeNode / #freebsd-gnome > http://www.FreeBSD.org/gnome >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051106052710.jn84zulfeo0k4g84>