RubyGems 1.1.0

Eric Hodel | Sat, 29 Mar 2008 08:41:00 GMT

Posted in ,

Announce: RubyGems Release 1.1.0

Release 1.1.0 adds some new features and fixes some bugs.

New features:

  • RubyGems now uses persistent connections on index updates. Index updates are much faster now.
  • RubyGems only updates from a latest index by default, cutting candidate gems for updates to roughly 1/4 (at present). Index updates are even faster still.
    • gem list -r may only show the latest version of a gem, add --all to see all gems.
  • gem spec now extracts specifications from .gem files.
  • gem query --installed to aid automation of checking for gems.

Bugs Fixed:

  • RubyGems works with both Config and RbConfig now.
  • Executables are now cleaned upon uninstall.
  • You can now uninstall from a particular directory.
  • Updating from non-default sources fixed.
  • Executable stubs now use ruby install name in shebang.
  • gem unpack checks every directory in Gem.path now.
  • gem install now exits with non-zero exit code when appropriate.
  • gem update only updates gems that need updates.
  • gem update doesn't force remote-only updates.
  • gem update handles dependencies properly when updating.
  • Gems are now loaded in Gem.path order.
  • Gem stub scripts on windows now work outside Gem.bindir.
  • gem sources -r now works without network access.

Other Changes Include:

  • RubyGems now requires Ruby > 1.8.3.
  • Release notes are now printed upon installation.
  • gem env path now prints a usable path.
  • gem install reverts to local-only installation upon network error.
  • Tar handling code refactoring and cleanup.
  • Gem::DependencyInstaller's API has changed.

For a full list of changes to RubyGems, see the ChangeLog file.

How can I get RubyGems?

NOTE: If you have installed RubyGems using a package system you may want to install a new RubyGems through the same packaging system.

If you have a recent version of RubyGems (0.8.5 or later), then all you need to do is: 

  $ gem update --system   (you might need to be admin/root)

(Note: You may have to run the command twice if you have any previosly installed rubygems-update gems).

If you have an older version of RubyGems installed, then you can still do it in two steps: 

  $ gem install rubygems-update  (again, might need to be admin/root)
  $ update_rubygems              (... here too)

If you don't have any gems install, there is still the pre-gem approach to getting software … doing it manually:

  1. DOWNLOAD FROM: rubyforge.org/frs/?group_id=126
  2. UNPACK INTO A DIRECTORY AND CD THERE
  3. INSTALL WITH: ruby setup.rb (you may need admin/root privilege)

To File Bugs

The RubyGems bug tracker can be found on RubyForge at: rubyforge.org/tracker/?func=add&group_id=126&atid=575

When filing a bug, gem env output will be helpful in diagnosing the issue.

If you find a bug where RubyGems crashes, please provide debug output. You can do that with gem --debug the_command.

Thanks

Keep those gems coming!

— Jim & Chad & Eric (for the RubyGems team)

10 comments

Comments RSS FEED

I had to take the ‘older version’ approach to successfully upgrade from 1.0.1 on Leopard (10.5.2):

$ sudo gem install rubygems-update
$ sudo update_rubygems
Jesse Newland said about 6 hours later

Worked fine for me (10.5.2), apart from a

Oh-no! Unable to find release notes

error message at the end.

Jan Foeh said about 11 hours later

@Jesse: I didn’t check to see if the release notes got shipped, oops! You’ll have to wait until the next release of RubyGems.

Eric Hodel said about 12 hours later

Installing via update—system did not work for me on 10.5.2 .

That installs a new executable in System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/bin/gem

/usr/bin/gem is a symlink pointing to System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/gem

Manually changing the link did not work: jan@jan-mbp:/usr/bin $ sudo ln -s ../../System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/bin/gem jan@jan-mbp:/usr/bin $ gem—version /usr/bin/gem:14: undefined method `ruby_version’ for Gem:Module (NoMethodError)

Jan said about 24 hours later

I got the same result as Jan did.

Sebastian Winkler said 2 days later

Actually, updating again using the ‘older version’ approach updated System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/gem and the error disappeared.

Sebastian Winkler said 2 days later

Oh-no! Unable to find release notes in: doc/release_notes/rel_1_1_0.rdoc - RubyGems installed the following executables: /usr/bin/gem - If `gem` was installed by a previous RubyGems installation, you may need to remove it by hand.

Doesn’t seem to work for CentOS 5. Complains about the release notes, says it has installed an executable, and that if a previous version existed it may need to “be removed by hand” (how?).

Anything done with /usr/bin/gem reports: /usr/bin/gem:14: undefined method `ruby_version’ for Gem:Module (NoMethodError)

jt said 5 days later

@jt: See my message above about why it can’t find the release notes. If you open a bug report as described above, I can help you with your other problem.

Eric Hodel said 5 days later

Done. Thanks, Eric.

jt said 6 days later

10.5.2—the regular gem update won’t do it (because of the symlink stuff above), but if you use the old version method (like Jesse – first comment) it will work.

To make sure it worked type ‘gem—version’. You should see ‘1.1.0’. If it didn’t work, try installing it the normal way and then the old version way again. :)

Justin said 12 days later

Comments are disabled