Update all gems after upgrading Ruby 2.0.0 version?

Ruby
1

I just upgraded Ruby 2.0.0-p247 to Ruby 2.0.0-p353 using rbenv install 2.0.0-p353 but now I don’t have any gems for that version. I’m new to
Ruby is it honestly required that the complete gemset has to be
reinstalled for every point release upgrade or is there a way to
copy/transfer/install the gems from the prior point release? Perl/CPAN
was so much easier :frowning:

gvim

2

On Sun, Dec 22, 2013 at 5:44 PM, gvim [email protected] wrote:

I just upgraded Ruby 2.0.0-p247 to Ruby 2.0.0-p353 using rbenv install 2.0.0-p353 but now I don’t have any gems for that version. I’m new to Ruby
is it honestly required that the complete gemset has to be reinstalled for
every point release upgrade or is there a way to copy/transfer/install the
gems from the prior point release? Perl/CPAN was so much easier :frowning:

gvim

I use RVM, not rbenv, but I’ve discovered the communal plugin, which
seems
to allow sharing gems between versions:

3

How do you know that your old gems are compatible with the new Ruby
version?

Henry

4

On 24/12/2013 00:44, Henry M. wrote:

How do you know that your old gems are compatible with the new Ruby version?

Henry

Well, coming from Perl, I’m assuming this isn’t an issue with
patch-level releases. I would expect to use the same @INC with Perl
5.16.1 and 5.16.2 without any issues.

gvim