RubyGems changes to accomodate multiple ruby implementations

Vít Ondruch vondruch at
Tue Nov 20 10:43:48 UTC 2012

Dne 20.11.2012 11:31, Charles Oliver Nutter napsal(a):
> On Tue, Nov 20, 2012 at 10:19 AM, Bohuslav Kabrda <bkabrda at> wrote:
>> There is a small regression hidden in this: The gems installed with "sudo gem install" currently place their extensions under /usr/local/lib64/gems/exts, which would also change to /usr/local/lib64/gems/ruby, causing these gems to need reinstallation if my changes are applied, but I don't think this should keep us from doing this transition.
> I don't think anything can keep you from doing this transition, since
> exts will never be portable across 32/64 or MRI/Rubinius or
> 1.8/1.9/2.0 C kinda just has to happen if there's going to be
> support for multiple installed Rubies on a single system.
> I did not see you mention different locations for 1.8 versus 1.9
> versus 2.0 exts...they are also not generally portable.

We do not plan to support multiple MRI versions. So there is no need for 

However, this might or might not come into play for Rubinius. But if 
that will be needed, the gems should go into 
/usr/lib[64]/gems/rubinius/{1.8,1.9,2.0} probably. In that case the line 
[1] will need some additional tweaks. But the important is that the rest 
of gems will stay untouched.



More information about the ruby-sig mailing list