KDE4/Mac Binaries

So I’ve finally gotten things pretty much set up for autobuilding KDE4/Mac packages. Universal packages for 10.4 are available here and I’m working on getting 10.3 packages put together as well. I’m still setting off the build process manually for now so I can watch it, but assuming things work out, they should start updating nightly sometime in the next few days. (Well… Assuming everything builds, of course.)

I’ve noticed there are some endianness issues with the png code, I need to figure out if it’s in libpng or somewhere higher up, but other than that, I was able to actually open Konqueror and browse around. Things are a little more stable than my last report a few months ago, so it looks like kde is moving in a generally forward direction. 🙂

If you have any questions, comments, whatever, please e-mail me or visit us on IRC.

Share on Facebook

Share on Facebook

Smooth Sailing with Leopard

So we’ve been working frantically to get Fink things up and running in a basic way on Leopard. I’m told that Fink HEAD now bootstraps cleanly, and we’ve been slowly working our way through smoke-testing building various things.

For the most part, it’s been really smooth, compared to this time in the previous cycle. The Tiger WWDC preview was nearly unusable; it was enough to get a taste of things to come, but so much was broken at the system level that it was hard to get things working reliably. It took a number of seeds before we could really do much work on 10.4.

That’s definitely not the case on Leopard. Other than a few minor buglets, stuff has been working remarkably well. I’ve probably only had to tweak maybe one in ten packages to get where I am, and those have been minor changes (mostly standard fixes related to POSIX compliance — “#include <sys/types.h>” and such).

I’ve managed to get a decent amount of KDE/X11 built, and it seems to run just fine:

Woot!

Share on Facebook

Share on Facebook

Out with a Bang, In with a Whimper

It’s funny how what should have been one of the greatest open-source PR moves since Netscape opened up the mozilla codebase instead feels like “too little, too late.”

Apple has announced Mac OS Forge, a project to do what OpenDarwin was already essentially created to do. It comes on the heels of months of bad PR about Apple failing to put out the X86 kernel source, and OpenDarwin shutting down due to a lack of communication between Apple and the open-source community and a lack of community involvement in general (other than a few specific exceptions like dports and WebKit).

For a company that’s done a great job of getting developers excited about their platform, this really shows they don’t understand the community they’re trying to get help from.

The most important thing you can give an open-source developer is the feeling that he’s doing something with impact; that he’s donating his time to something that others will appreciate and find useful. He wants to know that the work he’s doing goes, maybe not into the public domain, but into a world where everyone can stand on each other’s shoulders to . . . → Read More: Out with a Bang, In with a Whimper

Share on Facebook

Updates since June 29th

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 fastercsv-rb: new package (fast CSV parsing for Ruby) ferret-rb: new package (a port of the Lucene search engine to Ruby) gecko-sharp: updated to use firefox1.5 instead of firefox (1.0.x) gnupg and gnupg-idea: updated to 1.4.5 glitz: updated to 0.5.6 gst-plugins-bad-0.10: dependency fixes gst-plugins-base-0.10: updated to 0.10.9 gst-plugins-good-0.10: updated to a 0.10.4 snapshot (for updated OSX drivers) gst-plugins: dependcy fixes gstreamer-0.10: . . . → Read More: Updates since June 29th

Share on Facebook

Fink on Rails

So this last week I was at OSCON. I met a lot of awesome people, some of whom I’d met online and finally got to see in person. I also learned a ton about a lot of things, but really, The Buzz® was Rails, Rails, Rails.

I’ve played with Ruby on Rails off and on for a few months, and I was very impressed, but I learned a new appreciation for it at OSCON. There were a ton of good training classes and experts able to explain the stuff that up until now I’d been using without really knowing what it means… (which is common if you’ve just picked up the 15-minute demo and thought “man, that’s cool, I want to try it!”)

Of course, I hate having anything installed on my system without it being package-managed, so I went ahead and packaged up everything up to Rails as well as a few extras — Streamlined (a featureful replacement for the scaffold that was just announced at OSCON), and ferret (a port of the excellent Lucene search engine to Ruby).

It’s dead easy to package . . . → Read More: Fink on Rails

Share on Facebook

GNOME ABI is always backwards-compatible, except for when it’s not

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 convenience of framework developers. It’s not like there aren’t ways to consolidate the code that doesn’t break binary-compatibility.

And here I was going to help Daniel Macks work on . . . → Read More: GNOME ABI is always backwards-compatible, except for when it’s not

Share on Facebook

OSCON 2006 — Say “Hi”

I’m here in Portland at OSCON until Friday night. If you’re here, send me an e-mail and we can try to find each other and say “hi”. I’ve gone ahead and set up a “Birds of a Feather” meet-up, at 8:30pm Wednesday night, in room F150. If you’re interested in Fink, give us a visit.

If you’re not at OSCON, well, you’re missing out. 😉

Share on Facebook

Share on Facebook

Qt 4.2 and kdesupport snapshots updated

I’ve updated my universal packages for Qt and kdesupport to handle the latest that’s going on in kdelibs trunk (the move to Qt 4.2 snapshots, D-Bus moving from kdesupport to Qt, etc.) You should be able to build kdelibs trunk with these packages, until things change again. 😉

Share on Facebook

Share on Facebook

Major Java Updates

I've gone through a huge number of the java packages I maintain, and updated them en-masse. Besides version updates (and a number of new packages) the biggest change is that I normalized them all to target the 1.4 JDK. When Apple changed the default JDK to 1.5, we ended up with some strange issues because of compiling java code using the 1.4 JDK when some jars have been built with the 1.5 JDK.

A few of them (hsqldb, xerces-j-docs, xalan-j-docs, and I think one or two more) require that you build them with a terminal created by a logged-in user, so ssh'ing in to build, or building in a screen session, could fail. Be forewarned. 😉

Continue reading Major Java Updates

Share on Facebook Share on Facebook

Qt 4.1.4 and kdesupport snapshots

If you haven’t checked lately, I’ve been updating my Qt and kdesupport installer packages pretty regularly. If you’re interested in trying out KDE4 development, all you need is the Qt and kdesupport packages here, and CMake (2.4.2 or higher).

Things are starting to settle down from the D-Bus move and it looks like things are building pretty well.

I’ve updated my continuous build systems so that they work again, you can track whether it currently builds on my G4 10.3 box or an intel iMac here.

Share on Facebook

Share on Facebook