Home → Problems →

prerelease gems not listed when --all option is used

• Edit

thewoolleyman

01 Feb, 2010 04:43 AM

$ gem list bundler -a -r --prerelease

REMOTE GEMS

bundler (0.8.1, 0.8.0, 0.7.2, 0.7.1, 0.7.0, 0.6.0, 0.5.0, 0.4.1, 0.4.0, 0.3.1, 0.3.0)

$ gem list bundler -v 0.9.0.pre2 -r --prerelease

REMOTE GEMS

bundler (0.9.0.pre2, 0.9.0.pre1, 0.7.3.pre2, 0.7.3.pre)

$ gem env RubyGems Environment:
- RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0] - INSTALLATION DIRECTORY: /Library/Ruby/Gems/1.8 - RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS:

- ruby
- universal-darwin-9

• GEM PATHS:
  • /Library/Ruby/Gems/1.8
  • /Users/woolley/.gem/ruby/1.8
  • /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8
• GEM CONFIGURATION:
  • :update_sources => true
  • :verbose => true
  • :benchmark => false
  • :backtrace => false
  • :bulk_threshold => 1000
  • :sources => ["http://gems.rubyforge.org/", "http://gems.github.com"]
  • "gemcutter_key" => "19a8e0f7013b2ab262fbc4cd6d4bb6b6"
• REMOTE SOURCES:
  • http://gems.rubyforge.org/
  • http://gems.github.com

1. Support Staff 1 Posted by Nick Quaranto on 02 Feb, 2010 12:40 AM

   

   As far as I can tell, this is by design. In indexer.rb, the specs index is made here:

   http://github.com/jbarnette/rubygems/blob/master/lib/rubygems/index...

   this calls released_gems in the SourceIndex, which rejects prerelease specifically:

   http://github.com/jbarnette/rubygems/blob/master/lib/rubygems/sourc...

   So right now I'm just following what RubyGems does...do you think this is a problem?

   • Edit

2. 2 Posted by thewoolleyman on 02 Feb, 2010 01:07 AM

   

   I'd say this definitely violates the principle of least surprise. If I specify --all and --prerelease, I'd expect to see all gems, including prerelease.

   Furthermore, does this mean there is no way to list remote prerelease gems without specifying a version? That seems broken.

   • Edit

3. Support Staff 3 Posted by Nick Quaranto on 02 Feb, 2010 07:04 PM

   

   Ok, so this sounds like something the rubygems team should look at, perhaps open up a ticket on their bug tracker and link back to this discussion.

   • Edit

4. 4 Posted by thewoolleyman on 10 Feb, 2010 02:04 AM

   

   Eric Hodel fixed this in r2402

   • Edit