On Oct 23, 2007, at 06:43 , Laurent Sansonetti wrote: > In Leopard, we didn't want to use a unique gem repository, because we > wanted to separate the pre-installed gems that ship with Leopard from > the gems that the user will install after. So Leopard comes with 2 gem > repositories, one inside the Ruby framework that contains all the > pre-installed gems, and another one in /Library which is empty by > default, but which is also the default repository. > > The second change-set adds the APPLE_GEM_HOME constant value to the > gems paths if it's defined. We in fact define this constant in > rbconfig.rb.
I am not fond of this part of the patch, since GEM_PATH avoids special casing per ruby/rubygems packager. > The third change-set simply adds the ruby version to the default gem > directory, which was probably an omission. Is this backwards compatible with 10.4 and earlier? I don't know much about frameworkized ruby on OS X. > These changes should only be effective when Ruby is available as a > framework (where the RUBY_FRAMEWORK_VERSION or APPLE_GEM_HOME > constants are defined), so other environments should not be affected. -- 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
