[ANN] RubyInstaller 1.9.2-p0 released - Newer DevKit and instructions
Luis Lavena
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://rubyinstaller.org/downloads
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 Katz said in his RailsConf 2010 keynote:
"Find something impossible, then do it"
Thank you.
--
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
Sonja Elen Kisa
You need to fix a quotation mark error in the download html page... it
currently is:
<li class="exe"><a href=http://rubyforge.org/frs/download.php/72170/
rubyinstaller-1.9.2-p0.exe">Ruby 1.9.2-p0</a></li>
And it causes an extra quotation mark in the url because one is
missing between href= and http:
Sonja <3
http://kisa.ca
On Aug 21, 12:18 am, Luis Lavena <luislav...@gmail.com> wrote:
> 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:
>
Leledumbo
release? Also the compatibility list of gems.
On Aug 21, 12:40 pm, Sonja Elen Kisa <sonj...@gmail.com> wrote:
> Congrats on the release!!!
>
> You need to fix a quotation mark error in the download html page... it
> currently is:
>
> <li class="exe"><a href=http://rubyforge.org/frs/download.php/72170/
> rubyinstaller-1.9.2-p0.exe">Ruby 1.9.2-p0</a></li>
>
> And it causes an extra quotation mark in the url because one is
> missing between href= and http:
>
> On Aug 21, 12:18 am, Luis Lavena <luislav...@gmail.com> wrote:
>
> > 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:
>
Boško Ivanišević
Congratuliations! Is there any list of gems installed with this
release? Also the compatibility list of gems.
> Sonja <3http://kisa.ca
On Aug 21, 12:40 pm, Sonja Elen Kisa <sonj...@gmail.com> wrote:
> Congrats on the release!!!
>
> You need to fix a quotation mark error in the download html page... it
> currently is:
>
> <li class="exe"><a href=http://rubyforge.org/frs/download.php/72170/
> rubyinstaller-1.9.2-p0.exe">Ruby 1.9.2-p0</a></li>
>
> And it causes an extra quotation mark in the url because one is
> missing between href= and http:
>
>
> On Aug 21, 12:18 am, Luis Lavena <luislav...@gmail.com> wrote:
>
> > Hello,
>
> > I'm very pleased to announce the release of RubyInstaller packages for
> > Ruby 1.9.2-p0.
--
Regards,
Boško Ivanišević
Christian MICHON
> Hello,
>
> I'm very pleased to announce the release of RubyInstaller packages for
> Ruby 1.9.2-p0.
>
1 small question though: is this normal/expected to still have folders
named 1.9.1 in the lib and gems hierarchy ?
--
Christian
Luis Lavena
> Congrats on the release!!!
>
> You need to fix a quotation mark error in the download html page... it
> currently is:
>
> <li class="exe"><a href=http://rubyforge.org/frs/download.php/72170/
> rubyinstaller-1.9.2-p0.exe">Ruby 1.9.2-p0</a></li>
>
> And it causes an extra quotation mark in the url because one is
> missing between href= and http:
>
Thank you, Jon fixed that, I guess bad copy and paste :-(
Jon
>
> 1 small question though: is this normal/expected to still have folders
> named 1.9.1 in the lib and gems hierarchy ?
Thanks!
Check out the 1st FAQ entry from ruby-core in their 1.9.2 announcement regarding the 1.9.1 "library compatibility version"
http://www.ruby-lang.org/en/news/2010/08/18/ruby-1-9-2-is-released/
Jon
Luis Lavena
It is explained in Ruby 1.9.2 release announcement:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/367983
":The standard library is installed in /usr/local/lib/ruby/1.9.1
This version number is "library compatibility version". Ruby 1.9.2 is
mostly compatible with the 1.9.2, so its library is installed in the
directory."
They meant to say compatible with 1.9.1, so that is why the folder
structure refers to 1.9.1
HTH,
Octagon
> Ruby 1.9.2-p0.
>
attached now. Thanks.
I would make some very minor changes.
Add 1.9.2 to http://rubyinstaller.org/. Currently ruby-lang proudly
announces 1.9.2 and advices to visit the ruby installer where 1.9.2 is
not headlined.
Explain what "scan" means in ruby "dk.rb init to automagically scan
for your installed Rubies" found in http://wiki.github.com/oneclick/rubyinstaller/development-kit.
My impression is
that it just checks if Rubies installed by installers are still there.
If it is correct, why not just say so?
Possibly, I would also make the example in config.yml easier to
follow, especially when init finds no Rubies. My best bet is to create
a separate config.yml.sample where it would not be necessary to
comment out sample lines.
I guess Ruby packaging is finally on par with the expectations of
Windows users. Amazing.
Jon
> attached now. Thanks.
Great to hear that you like how the newer DevKit is used. I want to hear how people are using it and any issues people are having before I lock down how the new DevKit installer will behave.
> Add 1.9.2 to http://rubyinstaller.org/. Currently ruby-lang proudly
> announces 1.9.2 and advices to visit the ruby installer where 1.9.2 is
> not headlined.
>
> Explain what "scan" means in ruby "dk.rb init to automagically scan
> for your installed Rubies" found in http://wiki.github.com/oneclick/rubyinstaller/development-kit.
> My impression is
> that it just checks if Rubies installed by installers are still there.
> If it is correct, why not just say so?
You're right that dk.rb first scans the registry to try to determine what Rubies you have installed on your system. It then pre-populates config.yml with that info.
If you think the wiki page can be made more clear, please make the changes. It's a wiki and we can always update if needed.
> Possibly, I would also make the example in config.yml easier to
> follow, especially when init finds no Rubies. My best bet is to create
> a separate config.yml.sample where it would not be necessary to
> comment out sample lines.
I'm not for adding another file and prefer that the comments in the generated config.yml be made more clear and act like an embedded sample. Perhaps I'm not understanding your feedback. Please explain in more detail what you're thinking.
> I guess Ruby packaging is finally on par with the expectations of
> Windows users. Amazing.
Nice. Please keep testing and giving feedback on how it can be made better.
Jon
Octagon
On Aug 23, 4:59 pm, Jon <jon.for...@gmail.com> wrote:
> Great to hear that you like how the newer DevKit is used. I want to hear how people are using it and any issues people are having before I lock down how the new DevKit installer will behave.
- There are no side effects and no global settings. This is also true
for the 7z ruby packages.
- It is an archive. Tools like Total Commander can see into it.
- It is clear what it does to Rubies. Thus, it is easy to enable -
disable - troubleshoot - have many - whatever.
I also use DevKit to build simple programs like MPlayer (without
fontconfig).
> If you think the wiki page can be made more clear, please make the changes. It's a wiki and we can always update if needed.
> > Possibly, I would also make the example in config.yml easier to
> > follow, especially when init finds no Rubies. My best bet is to create
> > a separate config.yml.sample where it would not be necessary to
> > comment out sample lines.
>
> I'm not for adding another file and prefer that the comments in the generated config.yml be made more clear and act like an embedded sample. Perhaps I'm not understanding your feedback. Please explain in more detail what you're thinking.
>
# This configuration file contains the absolute path locations of all
# installed Rubies to be enhanced to work with the DevKit. This config
# file is generated by the 'ruby dk.rb init' step and may be modified
# before running the 'ruby dk.rb install' step. To include any
installed
# Rubies that were not automagically discovered, simply add a line
below
# the triple hyphens with the absolute path to the Ruby root
directory.
#
# Example:
#
# ---
# - C:/ruby19trunk
# - C:/ruby192dev
#
--- [
q:/ruby
]
Since there are no installer installed Rubies, after init I had
--- []
Following the instructions verbatim, I tried
--- []
- q:\ruby
and some other variants.
I guess
# before running the 'ruby dk.rb install' step. To include any
installed
# Rubies that were not automagically discovered, simply add the
absolute
# paths to their root directories to the list after the triple
hyphens.
#
# Example:
#
# --- [
# C:/ruby19trunk
# C:/ruby192dev
# ]
would be better.
Luis Lavena
Actually --- [] translate to the provided example:
---
- A
- B
- C
Equals:
--- [A, B, C]
Or in new lines
> I guess
>
> #
> # --- [
> # C:/ruby19trunk
> # C:/ruby192dev
> # ]
>
> would be better.
>
The dashes for arrays is part of YAML specification. When any version
of RubyInstaller is found, array.to_yaml is output with that format,
not with []
So the example will be inconsistent with that option too.
Is hard to please all the options :-P
Jon
>
> Specifically, I like the following most:
>
> - There are no side effects and no global settings. This is also true
> for the 7z ruby packages.
The installer will likely use global settings in the sense that it will create entries into the registry indicating where it was installed, version info, etc. It will also have side effects in that it installs itself and will update any installed Rubies with override files if the user wants.
> - It is an archive. Tools like Total Commander can see into it.
I'm guessing you will _not_ be able to due this with the DevKit installer as the installer will use Inno Installer. That said, does Total Commander allow you to look inside the current SFX as it's simply a 7-Zip file?
We'll likely keep supporting both DevKit SFX's and installers similar to how we currently do things with the RubyInstaller .exe's and 7z's.
> - It is clear what it does to Rubies. Thus, it is easy to enable -
> disable - troubleshoot - have many - whatever.
Agreed. The only thing automagic I want the DevKit installer to do is (a) install itself into a directory, and (b) populate the registry with useful info so that it can be identified by 3rd party software. Everything that it does to installed Rubyies should be user selectable from the installer GUI.
> I also use DevKit to build simple programs like MPlayer (without
> fontconfig).
Nice!
> > If you think the wiki page can be made more clear, please make the changes. It's a wiki and we can always update if needed.
>
> I updated the installation - step 4 section.
Thank you.
> My config.yml file is
>
> ...<SNIP>...
> #
> # Example:
> #
> # ---
> # - C:/ruby19trunk
> # - C:/ruby192dev
> #
> --- [
> q:/ruby
> ]
>
> Since there are no installer installed Rubies, after init I had
>
> --- []
>
> Following the instructions verbatim, I tried
>
> --- []
> - q:\ruby
>
> and some other variants.
Unfortunately you missed that the embedded example did _not_ have the empty "[]" after the triple dashes.
That said, I agree with you from a ease-of-use perspective and want to investigate how the dk.rb install script can "eat" the empty "[]" if it can't find any installed Rubies. Users shouldn't have to know too much about YAML details. I had hoped the embedded example in the generated config.yml would be enough, but it looks like it may have been too subtle.
So I don't forget this, please open a new issue at http://github.com/oneclick/rubyinstaller/issues requesting something like "Remove empty [] from generated config.yml"
Thanks for your feedback!
Jon
Octagon
>
open SFX archives. When Ctrl-PgDown is pressed it ignores the file
extension and tries to open the file as an archive with all the
plugins it has.
> We'll likely keep supporting both DevKit SFX's and installers similar to how we currently do things with the RubyInstaller .exe's and 7z's.
>
happy.
> So I don't forget this, please open a new issue athttp://github.com/oneclick/rubyinstaller/issuesrequesting something like "Remove empty [] from generated config.yml"
Added.
Jon
>
> Added.
Check out my response to try an updated dk.rb version from http://github.com/jonforums/rubyinstaller/raw/dk-script-mods/resources/devkit/dk.rb
Back up your old config.yml and dk.rb first :)