From: Eric Hodel <drbrain@...7.net>
Date: 2009-04-21T07:25:12+09:00
Subject: Re: [ANN] RubyGems 1.3.2

On Apr 17, 2009, at 15:01, Emiel van de Laar wrote:
> On Apr 15, 2009, at 11:44 PM, Eric Hodel wrote:
>> = Announce: RubyGems Release 1.3.2
>>
>> 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".
>>
>> Release 1.3.2 fixes some bugs and adds some features.
>>
>> Select New Features:
>>
>> * RubyGems now loads plugins from rubygems_plugin.rb in installed  
>> gems.
>> This can be used to add commands (See Gem::CommandManager) or add
>> install/uninstall hooks (See Gem::Installer and Gem::Uninstaller).
>> * Gem::Version now understands prerelease versions using letters.  
>> (eg.
>> '1.2.1.b')  Thanks to Josh Susser, Alex Vollmer and Phil Hagelberg.
>
> Hi all,
>
> Thanks for another release of RubyGems. Today I've been toying with  
> the
> new version syntax, e.g. 0.0.5.rc1. Are there any more docs for this?
>
> I can now create 'prerelease' gems but I can't figure out how to find
> them with 'gem list'. Is there or will there be a flag for this?

This seems to be an omission on our part, please file a bug.

> How does it work in practice?
>
> Say I have a gem with version 0.0.4 installed from rubyforge. A
> prerelease version, 0.0.5.rc1, is uploaded to rubyforge and I run
> gem update. I expect it to skip prereleases per default and I should
> only explicitly install prereleases.

`gem install` and `gem update` have a --prerelease flag now that will  
install prerelease gems.  You must opt-in to prereleases.

> Once a prerelease is installed
> and a higher release, i.e. 0.0.5 comes out I expect update to install
> it. Correct?

Correct.