or Create a profile
01 Feb, 2010 04:43 AM
$ gem list bundler -a -r --prerelease
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
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:
- EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS PLATFORMS:
2 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:
this calls released_gems in the SourceIndex, which rejects
So right now I'm just following what RubyGems does...do you
think this is a problem?
3 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
4 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
5 Posted by thewoolleyman on 10 Feb, 2010 02:04 AM
Eric Hodel fixed this in r2402
Comments are currently closed for this discussion.
You can start a new one.
2 people watching.
No more actions from RubyGems.org or the discussion starter are required.
This discussion is private.
Only you and RubyGems.org support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
Powered by Tender™.