Updating rubygems on leopard

I choose to try gems out this way because every time I've installed Gems from source to some prefix other than /usr/lib it's managed to find some way to not work or be otherwise inconvenient.

This is not something unique to Debian based systems.Now that (according to the release notes) it correctly updates when installed to different prefixes I guess I'll try source a source install to /usr/local again. *Don't* install the packages supplied by your distro -- use upstream source and put things in /usr/local. Complain and whine to busy people who will blow you off. I have Ruby Gems installed in /usr/local/lib, because I have *Ruby* in /usr/local.I just ran into a new Ruby Gems 0.9.5 issue this morning as well: $ sudo gem install rmagick Password: Bulk updating Gem source index for: native extensions. Successfully installed rmagick-1.15.10 1 gem installed Firefly:~/Documents/weddingbook james$ ruby -rubygems -e 'require "RMagick"' /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such file to load -- (Load Error) from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:27:in `require' from /usr/local/lib/ruby/site_ruby/1.8/RMagick.rb:11 from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 27:in `gem_original_require' from /usr/local/lib/ruby/site_ruby/1.8/rubygems/ custom_require.rb:27:in `require' from -e:1 I'll go file a bug. If you're not going to put Ruby Gems in the same place as Ruby, you're going to have to go to a little extra effort.This raises two issues : 1- rubygems seems to not take care of gems that are already installed (during the dependency checking) 2- rubygems should try to install dependency gems locally before remotely. It's that it will never 'just' work until Ruby Gems allows for these types of distribution requirements and there's absolutely no reason it can't. As it is I still can't use it on production servers because I have no confidence it's not going to going to go mucking around in folders that don't belong to it.This latest update some how decided to install rubygems to /usr/local even though it was previously installed in /usr/lib and it moved it's gem cache from /var/lib/rubygems to /usr/lib/ruby/gems. Now I realize the paticular oddities of this are not necessarily Ruby Gems problems. Rather than using features provided by Ruby Gems (GEM_PATH), Debian (and I guess also Ubuntu since it also uses apt) instead chose to hack Ruby Gems.

(Runtime Error) Unknown command unknown_command [...]/rubygems/command_manager.rb:114:in `find_command' [...]/rubygems/command_manager.rb:103:in `process_args' [...]/rubygems/command_manager.rb:74:in `run' [...]/rubygems/gem_runner.rb:39:in `run' /usr/local/bin/gem:22 === Changes Select new features include: * Automatic installation of platform gems * New bandwidth and memory friendlier index file format * "Offline" mode (--no-update-sources) * Bulk update threshold can be specified (-B, --bulk-threshold) * New `gem fetch` command * `gem` now has "really verbose" output when you specify -v * Ruby 1.9 compatible Other changes include: * Time::today is deprecated and will be removed at a future date * `gem install --include-dependencies` (-y) is now deprecated since it is the default, use --ignore-dependencies to turn off automatic dependency installation * `gem.bat` and bin stubs on mswin platforms are improved and compatible with the One-Click Installer * Multi-version diamond dependencies only are installed once * Bulk index updates take less memory * -V now enables verbose instead of -v to avoid collision with -- version's -v * `gem install -i` makes sure all depenencies are installed * `gem update --system` reinstalls into the prefix it was originally installe in * `gem update --system` respects --no-rdoc and --no-ri flags * HTTP basic authentication support for proxies * Gem:: Specification#platforms should no longer be a String, use Gem:: Platfor:: CURRENT when building binary gems instead * `gem env` has more diagnostic information * require 'rubygems' loads less code * is gone, Ruby Gems now uses built-in defaults * `gem install --source` will no longer add --source by default, use `gem souces --add` to make it a permanent extra source * `gem query` (list) no longer prints details by default * Exact gem names are matched in various places * mkrf extensions are now supported * A gem can depend on a specific Ruby Gems version * `gem_server` is now `gem server` * `gemlock` is now `gem lock` * `gem_mirror` is now `gem mirror` * `gemwhich` is now `gem which` * `gemri` is no longer included with Ruby Gems * `index_gem_repository.rb` is now `gem generate_index` * `gem` performs more validation of parameters * Removed gem* commands are now replaced with stubs that warn * Custom rdoc styles are now supported * Gem indexer no longer removes quick index during index creation * Kernel#require only rescues a Load Error for the file being required now * `gem dependencies` can now display some information for remote gems === Special Thanks * Daniel Berger for win32 support and testing * Luis Lavena for win32 support and testing * Tom Copeland for help testing and releasing the new indexer * Wilson Bilkovich for the new Marshal index format * To the rest of the Ruby Gems bug reporters and patch contributors The full set of changes including contributors is included in the Change Log.

Please or register to post comments
If spammers comment on your content, only you can see and manage such comments Delete all

Updating rubygems on leopard introduction

Updating rubygems on leopard

Recent posts

03-Jan-2019 09:43
03-Jan-2019 16:56
03-Jan-2019 20:48
03-Jan-2019 22:41
04-Jan-2019 07:35