On Oct 29, 6:55 pm, Lucas Nussbaum <lu... / lucas-nussbaum.net> wrote:
> On 30/10/07 at 07:28 +0900, Gonzalo Garramuñï wrote:
>
> > Lucas Nussbaum wrote:
> >> On 24/10/07 at 05:14 +0900, Gonzalo Garramuñï wrote:
> >> (a.3) seems like the only choice if going for (a). Furthermore, it's how
> >> it works currently with normal software.
> >> I if ./configure ; make ; make install $RANDOM_C_APP, it installs to
> >> /usr/local/bin, and takes precedence over what's in /usr/bin.
> >> The only thing that need to change in Ruby to make this possible is
> >> cleanup/standardization of its installation paths.
>
> > Ah, okay.  You want a.3.  I thought you wanted a.1.  So... what's wrong
> > with the current paths?  As far as I can tell, a.3) is how Ubuntu works
> > right now.  I'm not sure I understand what you see wrong with ruby's paths.
>
> On the libraries front, I think that Debian's solution is "OK". We
> should just get the third-party libs out of /usr/lib/ruby/1.8 (in
> /usr/lib/ruby/vendor_ruby/1.8 like OpenSUSE) or somewhere else.

Not quite sure I get this. Why isn't it just:

  Using distro package manager (apt-get, yum, etc):

    /usr/lib/ruby/1.8/  <- ruby core and standard
    /usr/lib/ruby/site_ruby/1.8/  <- 3rd party
    /usr/lib/ruby/gems/1.8/  <- "tunnelled" gems

  Using manual install methods (make, setup.rb, gem):

    /usr/local/lib/ruby/1.8/  <- ruby core and standard
    /usr/local/lib/ruby/site_ruby/1.8/  <- setup.rb
    /usr/local/lib/ruby/gems/1.8/  <- gem

T.