Issue #5617 has been updated by Vit Ondruch.


Motohiro KOSAKI wrote:
>  What's happen if a user install non-rpm gems? If it's installed into
>  fedora's "dedicated directory", some ruby interpreter may access it
>  and makes SEGV.

I am not sure I understand your point, but I'll try to elaborate a bit. With this patch there are two scenarios:

1) The default is that everything works as it worked now. I.e. you download the Ruby tarball, you don't care about any configuration options, everything is installed in default including RubyGems under Ruby directory.

2) You are user who cares about duplication of system libraries or you may be like to share gems between two interpreters (with all the consequences), therefore there is this configuration option "--with-rubygemsdir" if user likes.

I see no chances that "random ruby interpreter may access some inappropriate gem and SEGV" unless the user explicitly wants.

If you are using RPM managed gems (but also other software), it gets installed into /usr. If you like to install your own software from tarball, it should go into /usr/local. Again, I see no chance to collide unless you explicitly want.

The main reason for Fedora for this switch is to avoid duplication of system libraries, e.g. to allow MRI and JRuby to share the RubyGems library itself. This switch is one step forward to achieve this goal.
----------------------------------------
Feature #5617: Allow install RubyGems into dediceted directory
https://bugs.ruby-lang.org/issues/5617

Author: Vit Ondruch
Status: Rejected
Priority: Normal
Assignee: 
Category: 
Target version: 


Hello,

I would like to propose my patch, which allows to optionally install RubyGems library into dedicated directory, out of the default Ruby directory structure. This should enable to easily share one RubyGems library by more Ruby implementations and avoids code duplication. I did this patch since Fedora prohibits duplication of system libraries [1], which would be the case if MRI and JRuby are installed in parallel.

Thank you for considering this patch.

Vit


[1] https://fedoraproject.org/wiki/Packaging:Guidelines#Duplication_of_system_libraries


-- 
http://bugs.ruby-lang.org/