RubyInstaller 1.9.2-p136 released

Ruby
1

Hello,

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

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

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

For verification, MD5 signatures are provided:

9ce7db70da006994888171a0b1c2e809 *ruby-1.9.2-p136-doc-chm.7z
756458ddf5af07381c50e931eec025c9 *ruby-1.9.2-p136-i386-mingw32.7z
8e8843963dae29a98ce3e2ba2ee111f1 *rubyinstaller-1.9.2-p136.exe

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

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

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

Only difference with official release is the applied patch to correct a
Win32::Registry bug that didn’t made it due timing.

The bug report:

= What is new?

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

== Updated compiler toolchain to GCC 4.5.1

This is in sync with latest DevKit release announced:

http://groups.google.com/group/rubyinstaller/browse_thread/thread/348cae99911975ba

== Friendly gem installation error messages for gems that require
compilation.

Most of the times, people find confusing the massive error messages
they receive when installing gems that require compilation and no
compiler toolchain available.

We customized this release to provide a nicer error message and
helpful instructions to the user where to obtain a compiler and what
to do with it.

Example:

C:\Users\Luis>gem install RedCloth
ERROR: Error installing RedCloth:
The ‘RedCloth’ native gem requires installed build tools.

Please update your PATH to include build tools or download the DevKit
from ‘Downloads’ and follow the instructions
at ‘Development Kit · oneclick/rubyinstaller Wiki · GitHub’

We hope with this message will be make things more easy for Ruby users
to figure out what is going on.

Regards,

Luis L.
AREA 17

Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupry

2

Hi,

2010/12/27 Luis L. [email protected]:

I found a minor problem when installing RubyInstaller package of Ruby
1.9.2-p136.
The installer creates Program Group named “Ruby 1.9.2-p0” instead of
“Ruby 1.9.2-p136”.
Is it intended?

Regards,
Park H.

3

On Dec 26, 11:06pm, Heesob P. [email protected] wrote:

Hi,

I found a minor problem when installing RubyInstaller package of Ruby
1.9.2-p136.
The installer creates Program Group named “Ruby 1.9.2-p0” instead of
“Ruby 1.9.2-p136”.
Is it intended?

Did you remove the previous 1.9.2-p0 installation?

1.9.2-p0 and 1.9.2-p136 share the same AppId (GUID) for registry
information, as it considers it an update.

One thing to mention is that is safe to uninstall the previous version
as the installer will not remove any file copied by the user into the
Ruby folder, only the files that were part of the installer manifest.

That is the only upgrade path available at the moment.

Regards,

4

2010/12/27 Luis L. [email protected]:

No, I just deleted the folder and Program Group.
After uninstalling and reinstalling, Program Group is now “Ruby
1.9.2p136”.

1.9.2-p0 and 1.9.2-p136 share the same AppId (GUID) for registry
information, as it considers it an update.

It would be nice if the installer can uninstall previous same AppId
version automatically.

Regards,
Park H.

5

On Dec 26, 11:47pm, Heesob P. [email protected] wrote:

It would be nice if the installer can uninstall previous same AppId
version automatically.

Indeed, is on the feature request list:

Patches are welcome :wink:

Regards,