Issue #5617 has been updated by Benoit Daloze.


Hello,

I would be very interested to have a way to tell RubyGems to install at a particular shared path by default (to avoid unnecessary duplication), but only for the gems which are not implementation-dependents (e.g.: C extension should be installed in an unshared path of course).

I think this should be done in RubyGems's code, instead of an option in the configuration process (it would also avoid to do the work for each implementation).

What do you think?

P.S.: The duplication is especially bad since it means I must install all my (n) dependencies on every implementation/version when I want to test on them, which means m*n `gem install` (or worse, fetching the repository) which could just be n if the gems contain only implementation-independent code.
----------------------------------------
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/