Using the new 'ri'

ruby-talk
1

Folks,

Many of you know that ‘ri’ has undergone some change recently. Maybe
not Ruby 1.8.1, but from 1.8.2 onwards, ‘ri’ will be part of every
Ruby installation. This is convenient, but you may have to play a
part in generating its database.

If you are not sure what the latest is in this cool little program, I
put up this page to get you started. It only applies to people who
are happy to build the Ruby source from CVS at this stage.

http://www.rubygarden.org/ruby?NextGenerationRi

Gavin

2

Gavin Sinclair wrote:

Many of you know that ‘ri’ has undergone some change recently. Maybe
not Ruby 1.8.1, but from 1.8.2 onwards, ‘ri’ will be part of every
Ruby installation. This is convenient, but you may have to play a
part in generating its database.

If you are not sure what the latest is in this cool little program, I
put up this page to get you started. It only applies to people who
are happy to build the Ruby source from CVS at this stage.

http://www.rubygarden.org/ruby?NextGenerationRi

Gavin

Thanks for writing this up. It may be worth noting on your Wiki page
that the HEAD of the CVS repository is for Ruby 1.9, which I understand
will be a little experimental at this point (true?) In that case, people
may want to check out the 1.8 branch instead, e.g.

 cvs co -r ruby_1_8 ruby

Hope this helps,

Lyle

3

Do you know if it is possible to get a reproducible export from a branch by
using both -r and -D (date) options?

Eg how can I export the ruby_1_8 branch as it was on, say, 2004-01-01 ?

Andrew Walrond

···

On Saturday 10 Jan 2004 5:31 pm, Lyle Johnson wrote:

Thanks for writing this up. It may be worth noting on your Wiki page
that the HEAD of the CVS repository is for Ruby 1.9, which I understand
will be a little experimental at this point (true?) In that case, people
may want to check out the 1.8 branch instead, e.g.

 cvs co -r ruby_1_8 ruby