Congratulations to the Mono team on getting 2.0 released!Share on Facebook
Sure, it may seem quiet, but oh man, there’s been a lot going on.
First of all, a little off topic… Hockey season has started again. Go ‘Canes! <grin>
Second, as you might or might not be aware, a new kitty is coming to town soon. While David Morrison has done the majority of the work, I’ve been trying to help clean up some loose ends in getting things ready in Fink — validator fixes, working around compiler issues, and other misc stuff.
Third, I and a few other folks have been working on finally getting GNOME up to 2.20 (including GTK+ 2.12) in Fink, which is a metric TON of work. GTK+ 2.8 introduced a dependency on Pango‘s Cairo backend, which has to bubble up into build-time dependencies for literally hundreds of Fink packages. Through a combination of brute force and some automation, this is now . . . → Read More: The Calm Before the StormShare on Facebook
There are quite a few updates since my last big post. Most notable are getting mono up-to-date (although monodevelop still doesn’t work), Ruby on Rails, and kde 3.5.4 (as of this post, it’s 10.4-only, my 10.3 build machine is still chugging through doing a final verification build, but it should be out in the next day or two).
actionmailer-rb: new package (for Ruby on Rails) actionpack-rb: new package (for Ruby on Rails) actionwebservice-rb: new package (for Ruby on Rails) activerecord-rb: new package (for Ruby on Rails) activesupport-rb: new package (for Ruby on Rails) amarok: updated to 1.4.1 (still no GStreamer engine…) boo: updated to 0.7.6.2237-4 cairo: updated to 1.2.0 cocoa-sharp: updated to 0.9.1 . . . → Read More: Updates since June 29thShare on Facebook
So I’m rather surprised by GNOME‘s response to a recent bug on symbol visibility on Mac OS X. One of the things GNOME has done very well in the past is to always preserve backwards-compatibility, and they’ve generally stuck to it (and when they haven’t, it’s been an accident, and has been remedied).
But given the comments on the bug, apparently ELF linking with indirect symbols is now the only officially supported way to compile GNOME libraries, and breaking ABI compatibility is OK as long as it doesn’t break any important platforms. (ahem)
I’m in favor of refactoring code to the proper places as much as the next guy, but this is breaking ABI, and should wait for gnome-vfs3. That’s the way it works, you’re making a compact with the user that as long as this major number doesn’t change, your old binaries should still work. It’s a shame that they’ll break that covenant for the purposes of the . . . → Read More: GNOME ABI is always backwards-compatible, except for when it’s notShare on Facebook
Finally got MonoDevelop working again. Looks like the last hurdle was mozilla — for some reason, gecko-sharp (or mono 1.1.10/1.1.11, or something) was bombing with the mozilla 1.7.5 libraries. I’ve changed the dependencies to use firefox instead, and everything works. (Yay!)
Amarok: updated to 1.3.7, changed to allow the choice of backends: xine, gstreamer, or both
amrnb: new package, a speech codec used for mobile phones
Cocoa#: resurrected package, a Cocoa interface for Mono
Gecko#: updated to use firefox libraries instead of mozilla
GStreamer: new packages for GStreamer 0.10 (gstreamer, gst-plugins-base, gst-plugins-good, gst-plugins-ugly)
IKVM: updated to 0.22.0.0
libgdiplus: updated to 1.1.11
liboil-0.3: new package, a CPU optimization library
libsmoke: resurrected package, library for making Qt language bindings
Mono: updated to 1.1.11
MonoDevelop: updated to 0.9 — and it even works 😉
Mono Tools: updated to 1.1.11Share on Facebook
Been doing a lot more to catch up on my Fink packages (and updates to a few that aren’t mine) and have been working on getting KDE 3.4.2 cleaned up in unstable.
amarok: updated to 1.3.1
boo: updated to 0.6
bundle-kde*: lots of cleanups to fix upgrades
cairo: updated to 1.0
glitz: fixed a minor libtool library issue
gstreamer & gst-plugins: updated to 0.8.11, modernized dependencies (libshout2, etc.)
kde/koffice i18n: fixed download issues
kdeaddons3: made a kdeaddons3 package (which includes kpackage and a few other misc. utilities)
kdepim3: really fix the kaddressbook/kmail crash this time (by using gpgme’s pthread implementation, instead of pth)
libbonobo2 & libbonoboui2: updated to 2.10.1
libcapsinetwork: updated to 0.3.0 (to go along with monopd 0.9.3)
md5deep: new package, MD5/SHA1/etc. toolShare on Facebook
Been working on doing test builds of the Gnome 2.4 stuff and looking for missing build dependencies; it’s starting to look *really* good. All of the major bugs seem to be worked out, only a few minor things until it’s releasable, if I had to bet. Also, I’ve made a newer xfree86 snapshot. If you’re running unstable on 10.3, you should be able to “fink install xfree86” after a selfupdate and get 188.8.131.521-2. This is roughly equivalent to the 4.4 release candidate that Torrey announced, although it’s a slightly newer CVS snapshot. Please let me know if you run into any problems with it, initial testing shows it to be pretty stable on my system.Share on Facebook
There’s an interesting discussion between Havoc Pennington (from RedHat) and Miguel de Icaza (from Ximian) on the issues of Gnome/KDE interoperability. Strangely, I find myself agreeing with both of them for the most part, although in the end I prefer KDE3 to Gnome 2 currently. One thing I don’t understand is that one of Havoc’s reasons for not liking KDE is the supposed duplication of code between Qt and KDE:
That said, we are on track to be *substantially* smaller and faster if we kill the duplication of platform in gtk vs. libbonoboui, speed up pixbuf handling, optimize fontconfig, and some stuff like that. kdelibs is *huge*, as is Qt, and they heavily duplicate each other.
It seems to me that this is an interesting point of view from someone who works on a framework that is entirely written in C. KDE makes very heavy use of subclassing, there is really not much duplication going on in the KDE codebase as far . . . → Read More: Interesting KDE vs. Gnome DiscussionShare on Facebook