L
Luis Lavena
Hey guys,
Sometimes is good to be wrong.
Back in 2008 I said that going MSI and WiX was going to be the best
option from the "Administrative point of view"
At the end, I ended neglecting the XML files that WiX uses on every
bumping of version of Ruby, all that because updating those XML
failed.
I take the responsibility of that, and was one of the things that
slowed (to snail speed would say) the development and release cycle of
Ruby Installer.
After my last weekend struggling with WiX, and even contributions by
Bosko with some WiX changes to make it work, I decided to drop it.
As replacement, I've decided to go back to the basic and the tool I
know best: InnoSetup.
Hacked some basic scripts and then updated those to do more stuff
automatically. Hooked back in Rake and...
We have preview1!!!
http://rubyinstaller.org/downloads/
What to expect from this version:
After installation, you can access Ruby from the program folder at the
Start menu of Windows.
From there, you can:
- Start an Interactive Ruby console (IRB), from where you can try
quick Ruby code.
- Start a command prompt with Ruby in the PATH. This is needed since
the installer do not modify your Windows PATH to not conflict with
previous installation.
- Access documentation links from Ruby-Doc.
Things to come soon:
- Offer an option to add Ruby to your PATH.
- Integrate Programming Ruby book (CHM)
- Integrate Ruby documentation in searchable way (CHM)
Quick FAQ:
Q: Why you uploaded those to rubyinstaller.org and not RubyForge?
A: Because are preview versions and very very alpha state. Even they
worked for me, doesn't mean will work on every environment. Wanted to
avoid all end-users download it and break their current environments.
Q: Can I install Ruby 1.8 and 1.9 at the same time?
A: Yes, Ruby 1.8 will be installed by default to C:\Ruby, while 1.9
will install into C:\Ruby19. This is by default since 1.8 and 1.9
offer a different API and will interfere with some RubyGems.
Q: Why the installers are so small?
A: Because they only contains Ruby and RubyGems
Q: What happened to all these nice things One-Click Installer had bundled?
A: These are no longer integrated, long to explain
Q: Why on earth no? Please explain
A: This version of Ruby has been built with MinGW (GCC), not Visual
Studio (VC6).
Original One-Click installers used VC6, a 12 years old compiler.
In the original installers, lot of gems and packages where bundled.
Some of those packages hasn't been updated in years. Some of those
lacks testing tools to ensure they work as expected with this version
of Ruby.
Instead of invest RubyInstaller Team's time on fixing those, we
decided to invest our time improving the user experience on Windows.
We acknowledge some gems will not work, and some others will not
install. That's why we provided a Development Kit and plan ease the
process.
The Development Kit contains the needed tools to compile or
successfully install gems that are not ready for this version of Ruby.
You can find the downloads in the link above.
Q: Got it, but what if I want those gems works now?
A: If they don't work out of the box with Development Kit installed,
please contact the gem Author and make them aware of this
compatibility issue.
Q: I've tried to contact the gem author and he said he don't have
windows to build a gem for me.
A: That's understandable. We can't force everyone have a Windows
license, a virtual machine and the time to release Windows binaries of
those gems.
For that purpose, RubyInstaller Team created "rake-compiler" tool.
http://rubyforge.org/projects/rake-compiler
http://github.com/luislavena/rake-compiler
With this tool they can compile and build gems for Windows users from
Linux or Mac OSX operating systems.
There are already other authors using it, so they can take a look to
those references for implementation:
http://wiki.github.com/luislavena/rake-compiler/projects-using-rake-compile=
r
Q: Cool, going to test it, what to do if I find a bug or suggestion?
A: Please submit those to RubyForge tracker:
http://rubyforge.org/tracker/?group_id=3D167
Q: What if I want to contribute to it?
A: You're welcome!
Documentation, patches, improve the process, all those are really
appreciated. Please join us at rubyinstaller-devel mailing list:
http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
Introduce yourself and what would you like to get improved, done or fixed.
We are a friendly bunch of users and developers that care about Ruby
on Windows
Q: Thank you!
A: Thanks to you! And don't forget to Vote for the website contest:
http://blog.mmediasys.com/2009/06/23/rubyinstaller-get-ready-to-vote/
Last but no least, I'll like to the people that contributed with
patches, code, ideas and feedback during this process. In no special
order:
Curt Hibbs
Gordon Thiesfeld
Lars Christensen
Roger Pack
Timothy Elliott
Bosko Ivanisevic
James Tucker
Fabio Akita
Dr Nic Williams
Cheers,
--=20
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=E9ry
Sometimes is good to be wrong.
Back in 2008 I said that going MSI and WiX was going to be the best
option from the "Administrative point of view"
At the end, I ended neglecting the XML files that WiX uses on every
bumping of version of Ruby, all that because updating those XML
failed.
I take the responsibility of that, and was one of the things that
slowed (to snail speed would say) the development and release cycle of
Ruby Installer.
After my last weekend struggling with WiX, and even contributions by
Bosko with some WiX changes to make it work, I decided to drop it.
As replacement, I've decided to go back to the basic and the tool I
know best: InnoSetup.
Hacked some basic scripts and then updated those to do more stuff
automatically. Hooked back in Rake and...
We have preview1!!!
http://rubyinstaller.org/downloads/
What to expect from this version:
After installation, you can access Ruby from the program folder at the
Start menu of Windows.
From there, you can:
- Start an Interactive Ruby console (IRB), from where you can try
quick Ruby code.
- Start a command prompt with Ruby in the PATH. This is needed since
the installer do not modify your Windows PATH to not conflict with
previous installation.
- Access documentation links from Ruby-Doc.
Things to come soon:
- Offer an option to add Ruby to your PATH.
- Integrate Programming Ruby book (CHM)
- Integrate Ruby documentation in searchable way (CHM)
Quick FAQ:
Q: Why you uploaded those to rubyinstaller.org and not RubyForge?
A: Because are preview versions and very very alpha state. Even they
worked for me, doesn't mean will work on every environment. Wanted to
avoid all end-users download it and break their current environments.
Q: Can I install Ruby 1.8 and 1.9 at the same time?
A: Yes, Ruby 1.8 will be installed by default to C:\Ruby, while 1.9
will install into C:\Ruby19. This is by default since 1.8 and 1.9
offer a different API and will interfere with some RubyGems.
Q: Why the installers are so small?
A: Because they only contains Ruby and RubyGems
Q: What happened to all these nice things One-Click Installer had bundled?
A: These are no longer integrated, long to explain
Q: Why on earth no? Please explain
A: This version of Ruby has been built with MinGW (GCC), not Visual
Studio (VC6).
Original One-Click installers used VC6, a 12 years old compiler.
In the original installers, lot of gems and packages where bundled.
Some of those packages hasn't been updated in years. Some of those
lacks testing tools to ensure they work as expected with this version
of Ruby.
Instead of invest RubyInstaller Team's time on fixing those, we
decided to invest our time improving the user experience on Windows.
We acknowledge some gems will not work, and some others will not
install. That's why we provided a Development Kit and plan ease the
process.
The Development Kit contains the needed tools to compile or
successfully install gems that are not ready for this version of Ruby.
You can find the downloads in the link above.
Q: Got it, but what if I want those gems works now?
A: If they don't work out of the box with Development Kit installed,
please contact the gem Author and make them aware of this
compatibility issue.
Q: I've tried to contact the gem author and he said he don't have
windows to build a gem for me.
A: That's understandable. We can't force everyone have a Windows
license, a virtual machine and the time to release Windows binaries of
those gems.
For that purpose, RubyInstaller Team created "rake-compiler" tool.
http://rubyforge.org/projects/rake-compiler
http://github.com/luislavena/rake-compiler
With this tool they can compile and build gems for Windows users from
Linux or Mac OSX operating systems.
There are already other authors using it, so they can take a look to
those references for implementation:
http://wiki.github.com/luislavena/rake-compiler/projects-using-rake-compile=
r
Q: Cool, going to test it, what to do if I find a bug or suggestion?
A: Please submit those to RubyForge tracker:
http://rubyforge.org/tracker/?group_id=3D167
Q: What if I want to contribute to it?
A: You're welcome!
Documentation, patches, improve the process, all those are really
appreciated. Please join us at rubyinstaller-devel mailing list:
http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
Introduce yourself and what would you like to get improved, done or fixed.
We are a friendly bunch of users and developers that care about Ruby
on Windows
Q: Thank you!
A: Thanks to you! And don't forget to Vote for the website contest:
http://blog.mmediasys.com/2009/06/23/rubyinstaller-get-ready-to-vote/
Last but no least, I'll like to the people that contributed with
patches, code, ideas and feedback during this process. In no special
order:
Curt Hibbs
Gordon Thiesfeld
Lars Christensen
Roger Pack
Timothy Elliott
Bosko Ivanisevic
James Tucker
Fabio Akita
Dr Nic Williams
Cheers,
--=20
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=E9ry