Re: Installer packages for MacOSX

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.

> 4 - the installer doesn't say where it's going to go (/usr/local/). I
> would never have installed it if I hadn't  read one of the posters say
> it goes there, the thought of it trashing or intermingling with my
> 1.6-as-shipped-by-apple version is too horrible to contemplate. A note
> would be very reassuring to the wary!

I'll make sure to fix that.

> 5 - if you could manage it... it would be very useful to be able to
> change the install location. It won't RUN from a different location, 
> but
> I would be able to install it to, say, /usr/local/stow/ruby18/.... then
> run stow to create symlinks so that ruby THINKS it's in /usr/local. 
> That
> would mean I could then uninstall it when I want to with a single
> command.

I believe there is an option in the installer that lets the user choose 
the installation folder. I'll check that out.
However, when installing from a package, Installer leaves a receipt, 
which contains references to all the files that were added to your 
system by that install. It should be simple to put together a uninstall 
script based on the receipt... I'll need to look into it though.

> 6 - it has dependencies on your local system:
>
> $ /usr/local/bin/irb
> dyld: ruby can't open library: /supp/lib/libreadline.4.3.dylib  (No 
> such file or directory, errno = 2)
> Trace/BPT trap

Whoops! :/ I guess *that'll* need to be fixed. Obviously, I'm not very 
experienced at this...

> I tried this first, because I wanted to know if it had readline 
> support.
> I think you linked against a libreadline you've installed locally, but 
> I
> think you could link against  the systems readline framework, how to do
> so is described here:
>
>   http://cherryville.org/8896/ruby_readline_for_mac.html
>
> I used his precompiled bundle, and now irb as-shipped has a history.
> Yeah!

I seem to remember using this once before... I'll check it out.

> (I'm using osx 10.2, btw)
>
> 7 - I would think it is really, really cool if you could get whatever
> kind of script/project that you used into the ruby 1.8 cvs tree, so 
> that
> any os/x developer who checked out the cvs tree could build a .dmg like
> you did, without having to figure it out themselves, because you'd
> already done the hard work...

This was mostly manual :) After patching, I compiled it, moved 
/usr/local to /usr/local.real, installed, and copied the installation 
tree over. But it should be possible to write a script that would do 
this a little more cleanly... Perhaps by editing the makefile to add 
another installation option, which copies the files an installation 
archive.

I would *really* like it if the patches that let tcltklib compile on 
macs would be added to the cvs. They don't affect other installations, 
so it shouldn't break anything, I would think, just fix it.

I'll try to fix things up a little, and get them looking a little 
better. We'll see how it goes. :) Thanks for the feedback!!

--Mark

> and thanks for doing the hard work, btw!
>
> Cheers,
> Sam
>
>