On 10/20/07, Austin Ziegler <[EMAIL PROTECTED]> wrote:
> 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.)

Somehow they think that that violates the FHS, or at least the debian
policy interpretation of it.

Look at the very end of:
http://pkg-ruby-extras.alioth.debian.org/rubygems.html

I can't say that I understand it, but that's what the Debian ruby
maintainers think.

-- 
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/
_______________________________________________
Rubygems-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rubygems-developers

Reply via email to