Browse files

Removed RVM from the README.

RVM has repeatedly refused to consider explicit requests not to interfere
with the Rubinius build process. Further, it has repeatedly broken support
for installing Rubinius. There is no reason to promote its use. There are
a number of other tools for installing and using Rubinius, as well as package
mannagers for every major OS distribution. Efforts to make these tools work
well with Rubinius or get packages for major OS distributions is a far better
use of time and effort.

Ultimately, we need a dedicated section in the Rubinius documentation to
explain the various ways in which Rubinius can be installed.
  • Loading branch information...
1 parent bf9c28e commit faba2a8c453181d279c8e08a6b4436e6b512db25 @brixen brixen committed Dec 10, 2012
Showing with 8 additions and 34 deletions.
  1. +8 −34 README
@@ -9,7 +9,7 @@ same standard libraries as Matz's Ruby implementation (MRI). Rubinius also
provides C-API compatibility for native C extensions.
Rubinius currently is compatible with Ruby version 1.8.7. Full support for Ruby
-version 1.9.3 is coming soon.
+version 1.9.3 is in progress.
Rubinius runs on Mac OS X and many Unix/Linux operating systems. Support for
Microsoft Windows is coming soon.
@@ -35,44 +35,18 @@ To install Rubinius, use the following steps:
When the install process finishes, follow the directions printed to the
terminal to add the Rubinius executable (bin) directory to your PATH.
-See Section 6. Language Modes below for more information about configuring
+See Section 5. Language Modes below for more information about configuring
Rubinius for different Ruby language versions.
-4. Installing Rubinius with RVM
-Rubinius can be installed using the Ruby Version Manager (RVM) project.
-To install Rubinius with RVM, use the following steps:
- 1. Ensure the latest RVM is installed
- 2. rvm install rbx
-To use Rubinius in the current shell session, run:
- rvm use rbx
-To make Rubinius the default interpreter in new shells, run:
- rvm use rbx --default
-The documentation for RVM is available at:
-See Section 6. Language Modes below for more information about the supported
-Ruby language versions. See the RVM documentation for how to install Rubinius
-with different language modes using RVM.
-5. Using RubyGems
+4. Using RubyGems
Rubinius comes with RubyGems built-in. To install a gem, run the following:
rbx -S gem install <gem_name>
-6. Language Modes
+5. Language Modes
Rubinius implements multiple Ruby language features in one executable. You can
select the language mode at runtime by passing the -X18, -X19, or -X20 command
@@ -88,27 +62,27 @@ enabled and which one is the default mode with configure options.
For example, to enable both 1.9 and 2.0 modes, with 1.9 the default, use the
follwing configure options:
-./configure --enable-version=1.9,2.0 --default-version=1.9
+ ./configure --enable-version=1.9,2.0 --default-version=1.9
The --enable-version option takes a comma-separated list of versions. The
--default-version option takes a single version. If only a single version is
enabled, setting the default version is redundant.
-7. Documentation
+6. Documentation
After installing Rubinius, run 'rbx docs' to access the built-in documentation
at any time.
-8. Tickets
+7. Tickets
Please file tickets for bugs or problems. The issue tracker is:
-9. Contributing
+8. Contributing
The Rubinius team welcomes contributions. For more information read the
CONTRIBUTING file in the root directory of Rubinius.

5 comments on commit faba2a8


postmodern replied Dec 11, 2012

👍 for not relying on Ruby Managers. FWIW, @dbussink already reviewed chruby's Rubinius installation instructions. Feel free to crib.

ddd replied Dec 11, 2012

A list of the specific interference points would probably be good, since if its just changing of build time settings, users should be able to do this on their own as they wish. Showing where the changes RVM makes to the build process that are incorrect, or cause rbx not to work would probably be a good thing to show, if rbx is dropping RVM support. I'm sure others will have questions as to what RVM specifically changes that breaks rbx so they know.

Would also give the RVM Project a chance to respond to specifics, should they choose to.

I agree with ddd. I count on RVM handling all of my rubies, and if Rubinius is not supported, I probably won't mess with Rubinius anymore, mostly out of laziness. I would like to know the specifics of what's wrong.

Ideally, this could be done without a flame war.


brixen replied Dec 11, 2012

Folks, this has nothing to do with Rubinius supporting RVM. RVM is an external tool. We provide a build system that is used by multiple OS packaging systems, multiple Ruby installer and switcher systems, and can be used by anyone to simply build and run Rubinius in the clone directory, or install if they wish. If RVM choses to support Rubinius, that is up to RVM.

ddd replied Dec 11, 2012

I realize that. You said that RVM interferes with the RBX build process, which can be modified even by users not using RVM. I was looking for a list of the things RVM does that breaks, interferes, or otherwise harms/hampers RBX's build process when installed using RVM.

Please sign in to comment.