Manually updating rubygems

Rated 3.86/5 based on 504 customer reviews

Your signing certificate and private key are typically stored in ~/.gem/gem-public_and ~/.gem/gem-private_respectively.

To build a certificate for signing gems: The cleanup command removes old versions of gems from GEM_HOME that are not required to meet a dependency.

Forward does not currently support 64bit versions of Ruby on Windows, so we recommend you install Ruby 1.9.3 or the 32bit version of Ruby 2.0.

Once it’s downloaded, double click the file to start the installer.

Because of this, existing installations of Ruby Gems would have to been updated before the switch of the certificate and give enough time for the change to spread (and people to update).

It says updating ~/.rvm/rubies/ree-1.8.7-2010.02/bin/gem and when I do "which gem" it points at ~/.rvm/rubies/ree-1.8.7-2010.02/bin/gem.

When I run "which gem" it points to the same file that rubygems just reported that it updated.

Make your own gem Gems with Extensions Name your gem Publishing your gem Security Practices SSL Certificate Update Patterns Specification Reference Command Reference Ruby Gems API Ruby API Ruby API V2.0 Run your own gem server Resources Contributing to Ruby Gems Frequently Asked Questions Plugins Credits The build command allows you to create a gem from a ruby gemspec.

So there must be another version of gem in the require path?

I can't see one though., but it doesn't switch you to that particular Ruby interpreter.

Leave a Reply