What does the new config.gems get you that the old $GEM_PATH and
$GEM_HOME does not?

See http://wiki.rubyonrails.org/rails/pages/HowToUseMultipleGemRepositories

I just have a global gems repo, and the wider use-any-gem
functionality of vendor/gems for all gems, not just rails,
by setting:
GEM_HOME to RAILS_ROOT/gems
and setting:
GEM_PATH to $GEM_HOME:<the rest>

What am I missing?

just
%mkdir gems gems/bin
%export GEM_HOME=gems

and so on.  See the web page above.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to