View Full Version : Distributing Ruby scripts via an "installer". How to?
Jan 22, 2009, 11:45 AM
To date, I've simply been sending out my Ruby scripts as downloadable .rb files and telling people (via install instructions, emails, phone calls and FAQ entries... ugg) how to and where to install them. However, this is getting old.
I just read about how to create a .dmg, and that process seems pretty painless.
However, I still need an installer app. Can this be Ruby? Can anyone explain the process?
Jan 22, 2009, 07:47 PM
Why not have a folder inside the DMG which simply aliases the folder which it is suppose to be copied into? Similar to how you install stand alone applications.
The only reasons I can see to have an installer would be
1. you have a lot of files that need to be moved (that are not in a folder by themselves)
2. you need to install something in a system folder which would require a root password.
Jan 22, 2009, 09:30 PM
...Similar to how you install stand alone applications.
Good one... I've not done this before!!!
The only reasons I can see to have an installer would be ...
...If you had as many non-computer literate people as I have... ;)
There is another folder with the same name that I require my scripts be installed into, but it's buried inside a .app in a completely different part of the file structure, and Murphy's law has proved true time and time again, as some bean head that won't take the time to read the written instructions, in red, in bold, and will manage to screw it up.
There is no system folder activity. The path would be
The volume name can vary, but the rest of it won't change.
I've been reading about the "Manual Install" process in the "Software Delivery Guide" in Xcode. It seems pretty straight forward. I haven't gotten that far yet. I like that I can add a license agreement that has to be clicked-thru.
Jan 23, 2009, 01:00 AM
Well I mean this is how you install most all applications on OS X... I would hope that would be self explanatory for most users.
Sorry, I don't have the knowhow to be a whole lot more specific.
I just think the easiest way would be to alias off the directory it is going to be placed in, and make the end user install it very similar to how they install apps in OS X. The problem would be if the user didn't have that specific directory... Without more specific info I cant tell you much more.