Re: Problems moving from ri1.8 to ri1.9.1

> I am running a Debian unstable GNU/Linux system and trying to move
> from ruby1.8 to ruby1.9.1. As part of the exercise I wanted to be able
> to use ri1.9.1 instead of ri1.8 but have had great trouble in trying
> to create the .ri files for 1.9.1.

I'd suggest installing the latest version of rdoc and rdoc-data.  I
*think* that will allow ri xxx to work with the appropriate version.


> An unrelated circumstance is an anomaly that I don't understand.
> Running 'ri1.8 File::new' and 'ri1.9.1 File::new' gives different
> results but I have only a single File/new-c.ri on the machine. Again,
> if someone can shed light on this I'd be very grateful.


They're different in the code...maybe you have one you know not of?
What's the patch for?
Thanks!
-rp

> -------------------------------------------
> --- /tmp/new1.8 2010-05-21 18:41:27.000000000 +0100
> +++ /tmp/new1.9 2010-05-21 18:41:55.000000000 +0100
> @@ -2,2 +2,4 @@
> - =A0 =A0 File.new(filename, mode=3D"r") =A0 =A0 =A0 =A0 =A0 =A0=3D> file
> - =A0 =A0 File.new(filename [, mode [, perm]]) =A0 =A0=3D> file
> + =A0 =A0 File.new(filename, mode=3D"r" [, opt]) =A0 =A0 =A0 =A0 =A0 =A0=
=3D> file
> + =A0 =A0 File.new(filename [, mode [, perm]] [, opt]) =A0 =A0=3D> file
> +
> + =A0 =A0 From Ruby 1.9.1
> @@ -6,7 +8,15 @@
> - =A0 =A0 ``r'') and returns a new +File+ object. See the description of
> - =A0 =A0 class +IO+ for a description of _mode_. The file mode may
> - =A0 =A0 optionally be specified as a +Fixnum+ by _or_-ing together the
> - =A0 =A0 flags (O_RDONLY etc, again described under +IO+). Optional
> - =A0 =A0 permission bits may be given in _perm_. These mode and permissi=
on
> - =A0 =A0 bits are platform dependent; on Unix systems, see +open(2)+ for
> - =A0 =A0 details.
> + =A0 =A0 ``r'') and returns a new +File+ object.
> +
> + =A0 =A0 Parameters
> +
> + =A0 =A0 See the description of class +IO+ for a description of _mode_. =
The
> + =A0 =A0 file mode may optionally be specified as a +Fixnum+ by _or_-ing
> + =A0 =A0 together the flags (O_RDONLY etc, again described under +IO+).
> +
> + =A0 =A0 Optional permission bits may be given in _perm_. These mode and
> + =A0 =A0 permission bits are platform dependent; on Unix systems, see
> + =A0 =A0 +open(2)+ for details.
> +
> + =A0 =A0 Optional _opt_ parameter is same as in <code.IO.open</code>.
> +
> + =A0 =A0 Examples
> -------------------------------------------
>
>
>