Eric Hodel
2/25/2009 7:02:00 PM
On Feb 25, 2009, at 10:32, 7stud -- wrote:
> Brian Candler wrote:
>> 7stud -- wrote:
>>> My gem questions usually go unanswered. In my
>>> short experience with the gem system, it is a ponderously slow(bulk
>>> updating) broken piece of junk.
>>
>> It was: on a 512MB system, rubygems would happily eat up all
>> available
>> memory and go deep into swap.
>>
>> However 1.3.x seems to have fixed that.
>
> ...but as you can see, installing 1.3.x is broken. Sort of a
> catch-22.
No, your ruby is missing Etc. RubyGems' reporting of this fact is
broken.