RubyInstaller 1.9.2-p0 released - Newer DevKit and instructions

Ruby
1

Hello,

I’m very pleased to announce the release of RubyInstaller packages for
Ruby 1.9.2-p0.

As usual, installer and 7z-packages are available at RubyInstaller
website
and RubyForge for download:

http://rubyforge.org/frs/?group_id=167&release_id=44412

For verification, MD5 signatures are provided:

414786eec364c0a5d30bfdf41d840d5e *ruby-1.9.2-p0-doc-chm.7z
b676e771dec15478daefd50dd9757003 *ruby-1.9.2-p0-i386-mingw32.7z
21bf42f7ec4b8a831c947d656509cddb *rubyinstaller-1.9.2-p0.exe

Installer is also digitally signed to avoid alterations and UAC
warnings.

You can read Ruby 1.9.2-p0 announcement and release notes at ruby-talk:

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/367983

= What is new?

Beyond what is covered by Ruby itself, we have our own set of
improvements:

== Updated compiler toolchain to GCC 4.5.0

We thought was about time to upgrade our toolchain from GCC 3.4.5

We have been testing extensively not only Ruby compilation but it’s
dependencies and gems with good results.

It is now time to make those changes official. Starting this release,
all
upcoming versions of RubyInstaller packages will be based in GCC 4.5.0

== Road to a better Development Kit

One common complain we hear about our DevKit is the complicated steps
required
to get it working.

We started the work towards an installer that follows the simplified
lines of
RubyInstaller itself and aims to provide the smoothest solution as
possible.

While the work on this installer is not completed yet, we have made
available
a self-extracting package (SFX) that – with some easy to follow steps
– will
install the newer DevKit into all detectable Ruby installations.

SFX packages are available at GitHub:

http://github.com/oneclick/rubyinstaller/downloads

Please read the installation instructions in our wiki:

http://wiki.github.com/oneclick/rubyinstaller/development-kit

After its installation, you will see a similar output when installing
any gem:

gem install json --platform=ruby
Temporarily enhancing PATH to include DevKit…
Building native extensions. This could take a while…
Successfully installed json-1.4.6
1 gem installed

Please remember some gems require 3rd party development components
(headers
and such). Check each gem documentation for details.

= Exciting times ahead of us

We strongly believe that mainstream Ruby adoption requires its best
Windows
support.

All the improvements listed above and the ones covered over past months
shows
an eager Windows community willing to play and adopt Ruby as language.

There are more things to be done to improve this, but people is getting
their
hands dirty and helping out others.

Most important, this wouldn’t be possible without the timeless
contributions of Ruby developers that believe in making Windows a usable
platform.

As Yehuda K. said in his RailsConf 2010 keynote:

“Find something impossible, then do it”

Thank you.

2

great job!

3

While the work on this installer is not completed yet, we have made
available
a self-extracting package (SFX) that – with some easy to follow steps
– will
install the newer DevKit into all detectable Ruby installations.

Nice. It worked. Much easier than the old way :slight_smile:

A few feedbacks:

  1. might want to rename ‘dk.rb’ as ‘install.rb’ or something along those
    lines.
  2. it didn’t find any ruby dirs for me on “init” for some reason.
  3. when doing ‘ruby dk.rb install’ without doing init first it might
    could use a more intuitive message than ‘config.yml not found’
  4. might be nice to have it ‘auto-run’ something, too, after extract
    time, something like ‘install.bat’ which prompts you for a directory,
    etc.

Thanks much!
-r

4

On Aug 21, 5:17 pm, Michel D. [email protected] wrote:

Indeed is wrong, as it assumes that the system drive is C:. Please
open a ticket at RubyGems tracker:

http://rubyforge.org/tracker/?atid=575&group_id=126&func=browse

Anyhow, 1.9.x should not be having issues expanding “~”, if it does,
the lack of either HOME, HOMEDRIVE+HOMEPATH or USERPROFILE might be
the issue.

One of these variables is required and is assumed a 2000/XP/Vista/
7/2003/2008 Windows user have defined.

Actually, rubygems.rb should refer to ENV[“HOMEDRIVE”].

As I mentioned over RubyInstaller list, File.expand_path(“~”) should
not have issues at all as internally is doing the same thing.

I would recommend not change these values and instead report the
issues to both Ruby-Core and RubyGems trackers.

5

Luis L. wrote:

On Aug 21, 5:17�pm, Michel D. [email protected] wrote:

Indeed is wrong, as it assumes that the system drive is C:. Please
open a ticket at RubyGems tracker:

http://rubyforge.org/tracker/?atid=575&group_id=126&func=browse

Done : 28494

6

Luis L. wrote:

Hello,

I’m very pleased to announce the release of RubyInstaller packages for
Ruby 1.9.2-p0.

Just for the record. In the file ‘rubygems.rb’ shipped with the
installer, line 500, the windows home drive is hard coded as ‘C:/’. This
should not be. If your home drive is not C: (quite rare, but happens for
me), you should modify this line.

Actually, rubygems.rb should refer to ENV[“HOMEDRIVE”].

Thanks to Luis for helping me out of this bug.

_md

7

On Aug 21, 4:57 pm, Roger P. [email protected] wrote:

While the work on this installer is not completed yet, we have made
available
a self-extracting package (SFX) that – with some easy to follow steps
– will
install the newer DevKit into all detectable Ruby installations.

Nice. It worked. Much easier than the old way :slight_smile:

Hello Roger,

A few feedbacks:

  1. might want to rename ‘dk.rb’ as ‘install.rb’ or something along those
    lines.

Sometimes I really wish you were less disperse.

This has been discussed at RubyInstaller group for the past month.
Feedback and observation were asked for the past 3 weeks even with you
involved in other threads in the group.

Anyhow, “ruby install.rb install” doesn’t sound good, install is an
action and “dk” is not, which sound better IMO.

  1. it didn’t find any ruby dirs for me on “init” for some reason.

Maybe because you didn’t use the installers and instead the 7z
packages. There is no way to detect that.

That is why is crearly indicated at the end of init that you should
manually add other Ruby installations that weren’t detected.

  1. when doing ‘ruby dk.rb install’ without doing init first it might
    could use a more intuitive message than ‘config.yml not found’

Good one, please open a Issue at GitHub:

  1. might be nice to have it ‘auto-run’ something, too, after extract
    time, something like ‘install.bat’ which prompts you for a directory,
    etc.

I believe that is the job of the installer. The SFX were created as
short-term alternative but by no means is the replacement of the
installer.

Thank you for the feedback.

8

Sometimes I really wish you were less disperse.

This has been discussed at RubyInstaller group for the past month.
Feedback and observation were asked for the past 3 weeks even with you
involved in other threads in the group.

Better late than never, I suppose.

Anyhow, “ruby install.rb install” doesn’t sound good, install is an
action and “dk” is not, which sound better IMO.

rubygems uses “setup.rb” if that helps.

Maybe because you didn’t use the installers and instead the 7z
packages. There is no way to detect that.

it doesn’t scan the path for ruby.exe’s?

That is why is crearly indicated at the end of init that you should
manually add other Ruby installations that weren’t detected.

It could have used a better error message that it had detected none
than reporting success and writing a blank config.

Thanks!
0r