In article <88201E45-7918-11D8-B9F8-000502FDD5CC / mac.com>,
Mark Hubbart  <discord / mac.com> wrote:
>On Mar 17, 2004, at 6:07 PM, Sam Roberts wrote:
>
>> 1 - I've been meaning to build 1.8 for ages, but haven't because I'm
>> lazy, and I'd rather be working on my ruby projects. Now that you did
>> this, I have ruby1.8 locally. So, its useful.
>>
>> 2 - great that the samples and ri docs are there!
>>
>> 3 - it doesn't have ruby/cocoa or ruby/aeosa, which I think are pretty
>> important for a ruby/os-x system
>
>I've tried to get rubycocoa it to compile and work properly... but with 
>no luck. I think perhaps it needs updating to work with panther. If I 
>could get it working properly, I would include it as an optional 
>install in the package.

I believe there is a patch for Panther at the rubycocoa site.

I'm running Ruby1.8.1 from the darwinports.  I got the Ruby-1.8.1 package 
and then the rb-cocoa package and after some bug reporting to the package 
maintainer (those bugs are fixed now) It compiled/installed just fine.  So 
it is possible to get it working with Panther - you might want to go to 
DarwinPorts and take a look at the rb-cocoa port, it contains the recipe 
you need to build rubycocoa.

....I think for now I'll stick with my current setup as I would like to 
play with ruby-cocoa.

Note to Apple if anyone there is listening: It would be great if you guys 
would include the Ruby-Cocoa bindings in the official Ruby's included in 
OSX.  Then we could develop Cocoa apps in Ruby and distribute them widely 
without having to worry that users might not have the right 
Ruby/Ruby-Cocoa versions available.

Phil