On Oct 21, 2007, at 06:14 , Donavan Pantke wrote: > So, I mentioned in an earlier thread about the ability to have a > second gem > directory, (I called it VENDOR_HOME) to store gems installed by a > system > package manager. The gem command will treat this as read-only, and > so won't > install or delete gems from this directory. This means we should be > able to > have our cake and eat it too! I'm guessing that, in this structure, > GEM_HOME > will be in /usr/local/lib (with binaries linked to /usr/local/bin), > and > VENDOR_HOME will be in /usr/lib (and packages install the binary > commands). > > In theory, the gem cache should be placed somewhere in /var (there > are quite a few places this could be, either /var/lib/gems or /var/ > tmp/gems sounds appealing to me) > > I'm heading out of town next week, but when I get back I'll work on > getting > VENDOR_HOME and so forth into RubyGems, unless of course someone > else wants > to tackle this. :)
What you propose sounds no different than setting GEM_PATH appropriately. -- 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
