On Mon, Mar 8, 2010 at 4:54 PM, David Calavera <david.calav...@gmail.com> wrote:
> I just did some modification to the Mac installer and I think now it could
> be ready for a first version.
> Here is the repo: http://github.com/calavera/jruby-mac-installer
> Basically, now it creates this directories structure when the package is
> installed:
> /Library/Frameworks
>    |
>    | -> JRuby.framework
>             |
>             | -> Versions
>                    |
>                    | -> Current
>                    |
>                    | -> VERSION_NUMBER
>                    ...

Wow, this looks pretty cool! :)

> where "Current" is a symlink to the latest version installed and it can be
> easily modified by the user.
> After the creation of the directories the installer modifies the user's
> .bash_profile file to add the Current path to the user's PATH. I grabbed the
> script to do this from python's mac installer so we should check the license
> compatibilities and mention them as authors.

Yeah, license stuff sucks but we have to do it...

> So, if anyone wanted to build the installer he has to run the script
> "build.sh" and pass the jruby's source directory and its version as
> parameters, i.e:
>     ./build.sh dev/jruby 1.5.0.dev
> it calls ant to create the distribution, installs the native launcher, and
> creates the dmg file.
> I've created one package for test that you can download from
> http://thinkincode.net/JRuby-1.5.0.dev.dmg. It's build with snow loepard so
> jruby is compiled with java 6 since ant delegates to the javac.version
> number.
> I think by the moment, and since it will be official any issue that you find
> could be added to the github's tracker.

That's great...does anyone else want to give this a try? I'll probably
pull it tonight and see how it "feels" as far as an installer goes.

On Mon, Mar 8, 2010 at 4:57 PM, David Calavera <david.calav...@gmail.com> wrote:
> 30 seconds after clicking the "Send" button I just found a bug XD, I'm
> installing the native launcher when the installer is been built but I should
> install it when the user is installing the package, it's a quite easy
> modification.

Sure, I suppose installing it *on* the target user's system is better,
but perhaps it doesn't make that much difference either?

- Charlie

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to