The Artima Developer Community
Sponsored Link

Ruby Buzz Forum
RubyGems 1.3.7

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Eric Hodel

Posts: 660
Nickname: drbrain
Registered: Mar, 2006

Eric Hodel is a long-time Rubyist and co-founder of Seattle.rb.
RubyGems 1.3.7 Posted: May 13, 2010 11:54 PM
Reply to this message Reply

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

Advertisement

rubygems-update version 1.3.7 has been released!

RubyGems is a package management framework for Ruby.

This gem is an update for the RubyGems software. You must have an installation of RubyGems before this update can be applied.

See Gem for information on RubyGems (or `ri Gem`)

To upgrade to the latest RubyGems, run:

  $ gem update --system  # you might need to be an administrator or root

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

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 RubyGems 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

For more details and other options, see:

  ruby setup.rb --help

Changes

NOTE:

rubygems.org is now the default source for downloading gems.

You may have sources set via ~/.gemrc, so you should replace gems.rubyforge.org with rubygems.org

gems.rubyforge.org will continue to work for the forseeable future.

New features:

  • `gem` commands

    • `gem install` and `gem fetch` now report alternate platforms when a matching one couldn’t be found.

    • `gem contents` —prefix is now the default as specified in —help. Bug #27211 by Mamoru Tasaka.

    • `gem fetch` can fetch of old versions again. Bug #27960 by Eric Hankins.

    • `gem query` and friends output now lists platforms. Bug #27856 by Greg Hazel.

    • `gem server` now allows specification of multiple gem dirs for documentation. Bug #27573 by Yuki Sonoda.

    • `gem unpack` can unpack gems again. Bug #27872 by Timothy Jones.

    • `gem unpack` now unpacks remote gems.

    • —user-install is no longer the default. If you really liked it, see Gem::ConfigFile to learn how to set it by default. (This change was made in 1.3.6)

  • RubyGems now has platform support for IronRuby. Patch #27951 by Will Green.

Bug fixes:

  • Require rubygems/custom_require if —disable-gem was set. Bug #27700 by Roger Pack.

  • RubyGems now protects against exceptions being raised by plugins.

  • rubygems/builder now requires user_interaction. Ruby Bug #1040 by Phillip Toland.

  • Gem::Dependency support #version_requirements= with a warning. Fix for old Rails versions. Bug #27868 by Wei Jen Lu.

  • Gem::PackageTask depends on the package dir like the other rake package tasks so dependencies can be hooked up correctly.

Read: RubyGems 1.3.7

Topic: Igniting the Art of Fashioning Technology Previous Topic   Next Topic Topic: Quick ‘n dirty Lindo step for Cucumber

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use