From: Joshua Haberman <joshua@...>
Date: 2005-10-03T08:20:29+09:00
Subject: Re: why can't Ruby load .gem files directly?


On Oct 2, 2005, at 3:40 PM, Austin Ziegler wrote:

> On 10/2/05, Joshua Haberman <joshua@reverberate.org> wrote:
>
>> my-gem-dir/
>> my-gem-dir/foo-1.2.gem
>> my-gem-dir/foo-1.2-libfoo.so
>> my-gem-dir/foo-1.2-libbar.so
>> my-gem-dir/baz-0.3.gem
>>
>
> Except that my-gem-dir/foo-1.2-libfoo.so would *actually* be:
> my-gem-dir/i386-linux/foo-1.2-libfoo.so or something like that.
>
> Ruby and RubyGems solves a lot of this already.

Right, but the problem with RubyGems that I am trying to solve is  
that the interpreter can't load them directly.  (see the subject of  
this email).  I don't want to perform an "install" step.

If this functionality was supported, I believe a lot of the problems  
currently being debated would melt away.

Josh

P.S.  Incidentally, I don't see the point of the extra "i386-linux"  
directory.  What does it buy you?  I don't keep my C libraries in / 
usr/lib/i386-linux.  If shared objects are on my machine, it is  
assumed that they match the architecture of my machine.