On Oct 10, 2007, at 21:14 , Alex Ostleitner wrote: > As my 256MB VPS was swapping to death for hours (!) when attempting > to install any gem (while bulk updating the source it was eating > 300-350MB RAM), I attempted to install the beta gem as suggested by > Jim Weirich in a post in this list some months ago: > >> I would like those who are experiencing memory problems to give the >> beta version a try and report back. You can get the beta version > using >> (using sudo if necessary on your system): >> >> gem update --system --source http://onestepback.org/betagems >> >> Of course, if you are having problems due to memory, the above might >> not work. You can download the update explicitly using the following >> URL: >> >> http://onestepback.org/betagems/gems/rubygems-update-0.9.4.1.gem >> >> and then install locally. > > Never having installed a local gem before, I was a bit unsure how to > do so, and tried a simple "sudo gem install rubygems- > update-0.9.4.3.gem" from the folder I downloaded it to - which > successfully installed it, but I was still sitting at 0.9.4. > > After a hint in #ruby-lang I found out that I needed to unpack the > gem and then run "ruby setup.rb" to successfully update to 0.9.4.3.
update_rubygems is provided for this task. > Probably most of you know this. I'm just mentioning it here so people > might find it when googling for "gem memory problem". The memory problems should be largely fixed by trunk. There should be a beta this week. -- Poor workers blame their tools. Good workers build better tools. The best workers get their tools to do the work for them. -- Syndicate Wars _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
