From: Peter Vandenabeele <peter@...>
Date: 2011-11-19T20:12:52+09:00
Subject: Re: www.ruby-lang.org is back

--20cf300faf9bb6374704b2148848
Content-Type: text/plain; charset=UTF-8

On Fri, Nov 18, 2011 at 8:04 PM, R. Kumar <sentinel1879@gmail.com> wrote:

> > If I understand correctly:
> >
> > * 1.9.3-p0 is the current release version.  The -p0 means "patch number
> >   zero".
> >
> > * 1.9.3-head is the cutting-edge version in the main development
> >   repository, which may well include some incomplete feature additions
> > or
> >   changes.
> >
> > Someone correct me if I'm mistaken.
>
> I tried setting rvm's default to 1.9.3 without mentioning "-head"
> explicitly. Instead of using the -head installed already, it told me
> something like "you don't have -p0 installed." So is rvm always aware of
> the latest stable version?
>

rvm follows the latest "stable" version with a very small delay.

You can see which version rvm selects by default as follows:

$ rvm get latest
$ rvm reload
$ rvm list known
...
[ruby-]1.9.3-preview1
[ruby-]1.9.3-rc1
[ruby-]1.9.3[-p0]
[ruby-]1.9.3-head

The [-p0] indicates that at this time, the -p0 patchlevel is the
default patch level for ruby 1.9.3.

Before 1.9.3[-p0] , 1.9.3[-rc1] was the default for a certain time
(it changed from -rc1 to -p0 around 3 Nov 2011).

So yes, if you say e.g.

$ rvm use 1.9.3   # indicating 1.9.3-rc1 in October 2011

this was 1.9.3[-rc1] for a certain time, but when 1.9.3[-p0] comes out
and becomes the default, the same command

$ rvm use 1.9.3 # indicating 1.9.3-p0 now since Nov 2011

will suddenly fail if you had not yet installed 1.9.3-p0.

You can also upgrade all your existing gemsets from 1.9.3-rc1 to 1.9.3-p0
with

$ rvm upgrade ruby-1.9.3-rc1 ruby-1.9.3  # implicit ruby-1.9.3 is
ruby-1.9.3-p0

HTH,

Peter

--20cf300faf9bb6374704b2148848--