[Rubygems-developers] Is a remote list with --all supposed to be required to install older gem versions?

Eric Hodel drbrain at segment7.net
Tue Apr 1 15:01:25 EDT 2008

On Apr 1, 2008, at 03:06 AM, Chad Woolley wrote:
> On Mon, Mar 31, 2008 at 3:29 PM, Chad Woolley  
> <thewoolleyman at gmail.com> wrote:
>> On Mon, Mar 31, 2008 at 2:43 PM, Eric Hodel <drbrain at segment7.net>  
>> wrote:
>>> Caching bug.
>> Ticket: http://rubyforge.org/tracker/index.php?func=detail&aid=19228&group_id=126&atid=575
> I'm having real issues with the changes made in rev 1673.  It does not
> seem that the --all option always has an effect when listing gems,
> sometimes you still get only the latest version, even if you pass
> --all.   In GemInstaller, I have tests which exercise multi-version
> multi-platform installs, and they break with the changes in this
> revision.  If I revert this revision, everything works fine again.  An
> example failing test is
> http://geminstaller.rubyforge.org/svn/trunk/spec/functional/gem_runner_proxy_spec.rb 
> ,
> "should return output of gem command"
> If I add a call to 'reset' in Gem::SourceInfoCache.search, this also
> fixes the problem, but I think that also defeats the
> performance-improvement purpose of this revision.  I've spent a few
> hours trying to figure out how to fix the problem without rolling back
> the revision, but had no luck.  Trying to debug this caching code
> makes my eyeballs bleed...

Ok.  I've got one last test to run on the apple install problem, then  
I'll make this a top priority.  I already have your IM, so I'll ping  
you after lunch.

More information about the Rubygems-developers mailing list