Forum: Ruby RubyInstaller 2.0.0-p451 released

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
E7cff3cfd41c495e1012227d7dc24202?d=identicon&s=25 Luis Lavena (luislavena)
on 2014-02-25 06:28
(Received via mailing list)
I'm very pleased to announce the release of RubyInstaller packages for

Due sunset of RubyForge, we decided to migrate our main downloads to

Installers and 7z binary packages are available from

We would like to thank RubyForge and their mirrors for all the resources
provided through the years allowing users obtain our packages.

Taking in consideration the volume of data, old versions will remain at
RubyForge but no new package will be uploaded there.

## Ruby 2.0.0-p451

This new version of Ruby also brings new changes to RubyInstaller.

Starting with 2.0.0, the packages will be provided in two versions:
32bits (x86) and 64bits (x64).

This is possible thanks to newer compiler provided by mingw-w64 project.

This means newer DevKit package is required to use with this version.

### Important information

Please note that the installers in this release are *not digitally

You can read more about this in post at RubyInstaller group:

#### Choosing 32bits vs 64bits

Before you download a 64bits version, it is important you understand
not all gems, libraries or tools have been tested for this version.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as
is no performance issue around it.

#### Ruby 2.0.0 is brand new

While officially 2.0.0 is stable, that doesn't mean all the software
magically work on it.

Use 2.0.0 for development and verify your application, scripts and tools
properly before deciding to run this in your production environment.

#### Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 introduces ABI breakage which means compiled C extensions with
1.9.3 will work with Ruby 2.0.

**DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3, or try to use
extensions with it.**

You will be required to force compilation of those gems:

    gem install <name> --platform=ruby

This **will require you have the extra dependencies installed** for that
gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

#### Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

* Download and install `DevKit-mingw64-32-4.7.2` for 32bits Ruby 2.0.0
* Download and install `DevKit-mingw64-64-4.7.2` for 64bits Ruby 2.0.0

### MD5:

    4ee9c69517ad11b2b43f2aa3fb798f45 *ruby-2.0.0-p451-doc-chm.7z
    37feadb0230e7f475a8591d1807ecfec *ruby-2.0.0-p451-i386-mingw32.7z
    d4f6741138a26a4be12e684a16a19b75 *ruby-2.0.0-p451-x64-mingw32.7z
    9638024ea8a9095a70a4c521dd2ec2f6 *rubyinstaller-2.0.0-p451.exe
    af94b61c7113b79ae548d3363e59e5f1 *rubyinstaller-2.0.0-p451-x64.exe

### Official Announcement:

### Enhancements:

* Upgraded Ruby 2.0.0 to patchlevel 451
* Upgraded rb-readline to 0.5.0 (compatible with Ruby 2.0)
* Upgraded OpenSSL to version 1.0.0l
* Upgraded libyaml to version 0.1.5
This topic is locked and can not be replied to.