Hello,
I'm very pleased to announce the release of RubyInstaller packages for
Ruby 1.8.7-p334 and 1.9.2-p180
As usual, installer and 7z-packages are available at RubyInstaller
website and RubyForge for download:
http://rubyinstaller.org/downloads
http://rubyforge.org/frs/?group_id=167
For verification, MD5 signatures are provided:
3cd42e470f4ebd16310498c63bd52aeb *ruby-1.8.7-p334-doc-chm.7z
bc16f57f086915aaa8ad4116cb3fb7c2 *ruby-1.8.7-p334-i386-mingw32.7z
64e30e63e16028282fcfe3ec57b561dc *rubyinstaller-1.8.7-p334.exe
aecd3986b7c4281e000681b72c7386e8 *ruby-1.9.2-p180-doc-chm.7z
697aca4a83efe538aebe90939b529f20 *ruby-1.9.2-p180-i386-mingw32.7z
2c94aef50987416d64c85a4ea0fa428b *rubyinstaller-1.9.2-p180.exe
Installer is also digitally signed to avoid alterations and UAC warnings.
You can read Ruby announcements at the following links:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/378696
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/378699
= What is new?
Beyond what is covered by Ruby itself, we have our own set of improvements:
Enhancements from RubyInstaller:
* Upgraded RubyGems to 1.5.2 on all versions of Ruby
* Upgraded rb-readline to version 0.4.0
Regards,
···
--
Luis Lavena
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-Exupéry
This might be a silly thing to ask, but when I went through the 1.8.7 and
1.9.2 installers, it just started copying files into my existing C:\Ruby187
and C:\Ruby192 folders. Should it be mentioned that I need to uninstall the
old version first, or will this simply work fine overlaying new files and
deletes old, deprecated files from the previous patch release?
Newer patchlevels will not introduce newer files, it will only
accumulate changes (bugfixes) so is safe to install on top.
The only annoying part is that Start Menu item will not reflect the
latest patchlevel indication.
You can safely uninstall previous version (it will not remove any
installed gem or customization) and you can install latest patchlevel
on top.
Normally I'd be upgrading from a version that would install in a new folder
(Ruby 1.8.6 to 1.8.7 or 1.9.1 to 1.9.2), but since we're really only
upgrading patch-levels, I wasn't sure if there were things I need to be
aware of or things that might break if I'm not manually uninstalling the old
version first.
We have a feature request to make the install prompt and automatically
uninstall previous version, but since that depends on the installation
done with or without admin privileges make things a bit more
complicated.
In the meantime, you can safely install on top or uninstall if you
want the Start menu folder match the installed Ruby.
Regards,
···
On Sun, Feb 20, 2011 at 12:50 AM, Nick Klauer <klauer@gmail.com> wrote:
--
Luis Lavena
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-Exupéry