From: Lyle Johnson <lyle@...>
Date: 2008-04-11T23:31:38+09:00
Subject: Re: FXRuby versus Tk

On Fri, Apr 11, 2008 at 3:07 AM, Matt Mower <matt.mower@gmail.com> wrote:

>  Thanks for the advice. I confess I wasn't entirely surprised when the
>  rb-fxruby port didn't work for me:

<snip output>

Yes, that's due to a bug in the ruby port you're using. Trying doing:

    sudo port sync

to pull down the latest ports metadata, and then:

    sudo port update ruby

And finally,

    sudo port install rb-fxruby

>  I'm just reporting this FYI because I'm not planning to spend any more
>  time on this; I was only going to noodle about with Fox anyway and
>  messing with broken ports isn't my idea of fun.

I understand. MacPorts is great when it works, but it's sort of a
nightmare trying to support it. I like the idea of MacPorts building
things from source, but when your dependencies get out of whack it can
be a difficult problem to diagnose. There's something to be said for
the all-binaries packaging approach that most package managers take,
where someone else has already compiled the code and you have a better
shot of it working right off the bat. ;)

>  If I ever switch to Leopard Ruby I will be sure to give your binary gem a whirl.

Great!