On Jun 7, 2007, at 10:27, Randy Parker wrote: > [...] > > After some searching, I found [rubygems #8470] gem update --system > should take the prefix at which rubygems is installed into > accountwhich advises > > To workaround, switch to the downloaded rubygem update ( e.g. > GEM_HOME/gems/rubygems-update-0.9.2/), then run the install sequence > again: > > But in all cases the install step insisted on trying (and naturally > failing) to install to the hosting computer's system dir, with the > same line as included above: > > setup.rb:633:in `initialize': Permission denied - /usr/local/bin/ > gem (Errno::EACCES) > > Why is it attempting to install to the system when I'm telling it > not to?
Because the bug hasn't been fixed yet, and nobody's looked into fixing it. Note that the bug may be in setup.rb, which will take a bit of figuring out. Its quite the monster. -- 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
