From: Luis Lavena <luislavena@...>
Date: 2009-06-13T15:10:30+09:00
Subject: Re: Any plans for a Ruby 1.9.1 One-Click Installer?

On Jun 12, 10:01 pm, Christopher Dicely <cmdic...@gmail.com> wrote:
> On Fri, Jun 12, 2009 at 4:50 AM, Luis Lavena<luislav...@gmail.com> wrote:
> > On Jun 12, 2:05 am, Christopher Dicely <cmdic...@gmail.com> wrote:
> >> On Thu, Jun 11, 2009 at 8:08 AM, Gordon Thiesfeld<gthiesf...@gmail.com> wrote:
> >> > On Thu, Jun 11, 2009 at 12:28 AM, Christopher Dicely<cmdic...@gmail.com> wrote:
>
> >> >> Am I missing something, in either the archives or the instructions, or
> >> >> is the Ruby 1.9.1-p129 .7z archive missing all the ruby scripts that
> >> >> should be in /bin? It seems to work fine if one unpacks those from the
> >> >> 1.9.1-p129 source archive from ruby-lang after following the
> >> >> instructions you give, but I would assume that those should be
> >> >> included, not need to be brought in separately.
>
> >> > Are you talking about these?
>
> >> > erb
> >> > gem
> >> > irb
> >> > rake
> >> > rdoc
> >> > ri
> >> > testrb
>
> >> > I see them all in the bin dir of the .7z file.
>
> >> Huh. The only thing I see in ruby-1.9.1-p129-i386-mingw32\bin are the
> >> ruby.exe and rubyw.exe binaries, a bunch of .dlls, and the .bat files
> >> corresponding to each of the scripts you list each try to run ruby.exe
> >> and pass it the relevant script, but not the ruby scripts themselves.
>
> > Definitely there is a problem with what you unpacked.
>
> > I see irb and irb.bat, and all the other script files.
>
> The problem appears to have been with the version of ZipGenius I was
> using; it apparently misses files with no extension in .7z files (at
> least, it seems to with the ones from the rubyinstaller page.) I've
> never seen that with any of the other archive formats it supports, and
> its not a bug that I would have expected. Downloaded the 7-Zip
> application itself, and, indeed, the scripts are there.

Glad to hear that I didn't messed things up. Your comment forced me to
install 7zip on the office Mac just to verify I'm not crazy :-P

Please don't hesitate in open new threads with your questions about
using it, but should be pretty straight forward:

1) Unpack

2) Add "bin" folder to the path (example):
SET PATH=%PATH%;C:\ruby-1.9.1-p129-i386-mingw32\bin

3) Check ruby is working:

ruby -v

4) Check rubygems is working:

gem env

5) You're good to go :-)

--
Luis Lavena