This post originated from an RSS feed registered with Ruby Buzz by Eric Hodel. Original Post: RubyGems 1.3.0 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

Release 1.3.0 adds new features and fixes some bugs.

New features:

• RubyGems doesn’t print LOCAL/REMOTE titles for `gem query` and friends if stdout is not a TTY, except with—both.
• Added Gem.find_files, allows a gem to discover features provided by other gems.
• Added pre/post (un)install hooks for packagers of RubyGems. (Not for gem themselves).
• RubyGems now installs gems into ~/.gem if GEM_HOME is not writable. Use—no-user-install command-line switch to disable this behavior.
• Fetching specs for update now uses If-Modified-Since requests.
• RubyGems now updates the ri cache when the rdoc gem is installed and documentation is generated.

Deprecation Notices:

• Gem::manage_gems now warns when called. It will be removed on or after March 2009.

Bugs Fixed:

• RubyGems 1.3.0+ now updates when no previous rubygems-update is installed. Bug #20775 by Hemant Kumar.
• RubyGems now uses the regexp we already have for `gem list—installed`. Bug #20876 by Nick Hoffman.
• Platform is now forced to Gem::Platform::RUBY when nil or blank in the indexer. Fixes various uninstallable gems.
• Handle EINVAL on seek. Based on patch in bug #20791 by Neil Wilson.
• Fix HTTPS support. Patch #21072 by Alex Arnell.
• RubyGems now loads all cache files even if latest has been loaded. Bug #20776 by Uwe Kubosch.
• RubyGems checks for support of development dependencies for #to_ruby. Bug #20778 by Evan Weaver.
• Now specifications from the future can be loaded.
• Binary script uninstallation fixed. Bug #21234 by Neil Wilson.
• Uninstallation with -i fixed. Bug #20812 by John Clayton.
• Gem::Uninstaller#remove_all now calls Gem::Uninstaller#uninstall_gem so hooks get called. Bug #21242 by Neil Wilson.
• Gem.ruby now properly escaped on windows. Fixes problem with extension compilation.
• `gem lock—strict` works again. Patch #21814 by Sven Engelhardt.
• Platform detection for Solaris was improved. Patch #21911 by Bob Remeika.

Other Changes Include:

• `gem help install` now describes version argument to executable stubs
• `gem help environment` describes environment variables and ~/.gemrc and /etc/gemrc
• On-disk gemspecs are now read in UTF-8 and written with a UTF-8 magic comment
• Rakefile
• If the SETUP_OPTIONS environment variable is set, pass its contents as arguments to setup.rb
• lib/rubygems/platform.rb
• Remove deprecated constant warnings and really deprecate them. (WIN32, etc).
• lib/rubygems/remote_fetcher.rb
  • Now uses ~/.gem/cache if the cache dir in GEM_HOME is not writable.
• lib/rubygems/source_index.rb
• Deprecate options to ‘search’ other than Gem::Dependency instances and issue warning until November 2008.
• setup.rb
• —destdir folder structure now built using Pathname, so it works for Windows platforms.
• test/*
• Fixes to run tests when under test/rubygems/. Patch by Yusuke ENDOH [ruby-core:17353].
• test/test_ext_configure_builder.rb
• Locale-free patch by Yusuke Endoh [ruby-core:17444].

For a full list of changes to RubyGems and the contributor for each change, see the ChangeLog file.

Special thanks to Chad Wooley for backwards compatibility testing and Luis Lavena for continuing windows support.

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:

NOTE: RubyGems 1.1 and 1.2 have problems upgrading when there is no rubygems-update installed. You will need to follow the second set of update instructions if you see “Nothing to update”.

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:

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

1. DOWNLOAD FROM: http://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: http://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)