This post originated from an RSS feed registered with Ruby Buzz by Eric Hodel. Original Post: RubyGems Beta 0.9.0.8 Feed Title: Segment7 Feed URL: http://blog.segment7.net/articles.rss Feed Description: Posts about and around Ruby, MetaRuby, ruby2c, ZenTest and work at The Robot Co-op. Latest Ruby Buzz Posts Latest Ruby Buzz Posts by Eric Hodel Latest Posts From Segment7

Beta version 0.9.0.8 is now available with:

gem update --system --source http://onestepback.org/betagems

Merry christmas from the RubyGems project!

If you find any bugs, report them on the RubyGems bug tracker.

Upgrade note

While require_gem was deprecated in 0.9.0, the bin stubs are still using it (oops!). To get rid of the warnings printed by rake or other bin stubs simply reinstall the gem. In the next beta ‘gem pristine—all’ will fix all your gem bin stubs.

What’s new since 0.9.0?

Lots! Many changes both big and small! Here’s an incomplete summary:

• require_gem is deprecated and will print a warning. Use gem instead.
• RubyGems now requires ruby 1.8.2 or greater.
• gem command changes
  • new gem pristine command
  • new gem outdated command
  • new gem sources command
  • gem uninstall can uninstall multiple gems
  • gem install uses the cache instead of downloading
  • gem install returns non-zero exit code on failure
  • gem install can now set shebang on bin stubs (env or ruby)
  • gem help output now fits in 80 columns
• now -w clean
• many proxy installation improvements
• gem cert impromevents
• RubyGems is now easier to use as a library.
  • Easier programatic installs
  • Easier inspection of local and remote gems
• extension building enhancements
• error reporting enhancements (less odd exceptions)
• many bugs fixed or closed (0 bugs in tracker!)
• require now loads .jar files
• select bug fixes:
  • installing from scratch fixed
  • gem install—force forces
  • installing from read-only location works
  • gem uninstall requires full name
  • gem install obeys GEM_HOME for bin scripts
  • RubyGems now installs on ruby 1.9

For full details, read the ChangeLog.