The GNOME Project has just released the 2.10.0 version of its Desktop Environment. This is a new major release of the 2.x branch, which is source and binary compatible with all previous versions in the 2.x series.
Aside lots of fixes, improved translations and code cleanups, which are typical in minor releases, this one includes several new features and utilities designed to make your desktop experience better than ever. You can see a summary of changes here, and in case you are impatient to see it working, just download and try the live cd.
Now, the big question: when will this be ready for pkgsrc? Well, I've started working on the update a moment ago, and after a quick look, there are around 70 packages to go (several of which should be straightforward updates); as you can expect, this will take a while.
As we are on a feature freeze in order to prepare the next pkgsrc stable branch, 2005Q1, I'll have more than a week of time to work on it calmly (don't think that that's a long time). Unfortunately, this means that I won't be able to help much to stabilize the current code-base. Shame on me! I don't like to say this, but... pkgsrc freezes always come in bad timing (final exams or new GNOME releases), so I can't usually help :-(
[Originally posted at 2005-03-16 03:59 am UTC]
ReplyDeleteI did a gnome upgrade just before this release to the 2.8.x state (for some x) and I now suspect thats when my particular breakage with firefox now moving to GTK by default came in.
I never used to see gconf/gconf2 live, but now do, and firefox insists on talking to them for some CORBA stuff, and won't die if its *ever* been used to download an object, and pops up windows for flashes of time, so you can't see the diagnostic.
This isn't the libwallet.so thing, thats a known baddie. I think there is a gnome/firefox interaction going on.
I've never had audio working well under gnome, I am really interested in how well this new release folds in. My suspicion is that the only really good way to install gnome is to de-install it first, not to use make upgrade.
So I am taking that 'binary compatible' flag with a pinch of salt! :-)
-George