[Rubygems-developers] RubyGems 0.8.10 Prerelease Ready

[Curt Hibbs]

Jim Weirich wrote:
> Ok, I've got a version of RubyGems I'd like to release.  Considering the fact 
> that the last releases needed a quick fix after publicly announcing them, I'm 
> announcing them here first, with a view to doing a public announcement in day 
> or two (probably Sunday evening).
> 
> Two bug fixes in this release
> 
> (1) Better handling for pinning required versions of libraries (thanks to 
> Tobias Luetke for helping with this one).
> 
> (2) Better gem update --sysgem handling.
> 
> I would like some help testing (2), particularly on windows box (which I don't 
> have acces to at the moment).
> 
> Here's what you need to do to test (2).  Manually download (do not use the gem 
> update command here!) the 0.8.9.3 version of RubyGems from
> 
>     http://onestepback.org/betagems/gems/rubygems-update-0.8.9.3.gem
> 
> Then do a local install with it. Something like
> 
>   $ gem install rubygems-update-0.8.9.3.gem
>   $ update_rubygems
> 
> should do the trick.  Version 0.8.9.3 is essentially identical to version 
> 0.8.10, but with a smaller version number.  That allows us to do the 
> following command ...
> 
>   $ gem update --system --source http://onestepback.org/betagems
> 
> After that installs, double check that the gem command claims to be version 
> 0.8.10.
> 
>   $ gem --version       # should report 0.8.10
> 
> As I mentioned, I'm particularly interested that I didn't break how this works 
> on windows boxes.
> 
> I also attached the 0.8.10 announcement for review.
> 
> Thanks to everyone for their help.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> = Announce: RubyGems Release 0.8.10
> 
> Version 0.8.10 is bug fix release.  We address two bugs in this
> release, one obscure and the other only slightly annoying.
> 
> In multi-user environments, it is common to supply mulitple versions
> of gems (for example Rails), allowing individual users to select the
> version of the gem they desire.  This allows a user to be insulated
> from updates to that gem.  RubyGems 0.8.10 fixes a problem where gems
> could occasionally become confused about the current versions of
> libraries selected by the user.
> 
> The other annoying bug is that if there are any existing
> rubygems-update gems installed, then the "gem update --system" command
> will download a new udpate, but install the latest update prior to the
> download.  
> 
> == What is RubyGems?
> 
> RubyGems is a package management system for Ruby applications and
> libraries.  RubyGems one command download makes installing Ruby software
> fun and enjoyable again. (Ok, not really.)
> 
> Many gems are available for download from the RubyForge site.  Browse
> the list of gems with a "gem list --remote" command and download what
> you need with a simple "gem install <name-of-gem>".  RubyGems takes care
> of the details of installing, not only the gem you requested, but also
> any gems needed by the software you selected.
> 
> == RubyGems Statistics
> 
> * About 230 different gems available (I say _about_ because I don't
>   think "Bangkok" and "bangkok" are really different gems).
> * Over 30,000 downloads of the RubyGems software
> * 230,075 gem loads
> 
> If you are interested in finding out when new gems are released, I
> maintain an RSS feed at http://onestepback.org/gemwatch.rss.
> 
> == How can I get RubyGems?
> 
> 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: http://rubyforge.org/frs/?group_id=126
> 2. UNPACK INTO A DIRECTORY AND CD THERE
> 3. INSTALL WITH:  ruby setup.rb all  (you may need admin/root privilege)
> 
> == Thanks
> 
> Thanks to Tobias Luetke for reporting the problem and assisting in
> tracking it down.
> 
> Keep those gems coming!
> 
> -- Jim & Chad (for the RubyGems team)

It worked fine for me, too (on windows)!

Curt