On 10/20/07, Brian Sammon <[EMAIL PROTECTED]> wrote:
> > > def dir
> > > ### Debian ###
> > > [EMAIL PROTECTED] ||= nil
> > > set_home(ENV['GEM_HOME']) if ENV['GEM_HOME']
> > > @gem_home ||= File.join("/var/lib/gems",
> > > Config::CONFIG['ruby_version'])
> > > #set_home(ENV['GEM_HOME'] || default_dir) unless @gem_home
> > > ##############
> > > @gem_home
> > > end
> > I can't believe that they did that. There's better ways to do this
> > than they did.
> I'd be interested in hearing what the better ways are.
It's called "GEM_HOME". It's called submitting patches that allow
setup to provide a different default_dir. Hardcoding your directory is
bad news. (It should be /var/lib/ruby/gems if they're going to be
doing something that odd, anyway.)
> A few weeks ago I was looking to set up ruby on a windows box, and I wanted to
> have gems install into a directory outside of the ruby install directory (so
> they'd stay around when I upgraded ruby), and I ended up using the Debian hack
> because I couldn't find anything better.
That's not safe on Windows if you use any binary extensions.
-austin
--
Austin Ziegler * [EMAIL PROTECTED] * http://www.halostatue.ca/
* [EMAIL PROTECTED] * http://www.halostatue.ca/feed/
* [EMAIL PROTECTED]
_______________________________________________
Rubygems-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rubygems-developers
