>> 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?
>
> Actually this two patches are just subset of patches I'd like to introduce into Fedora. You can find all the patches in my repository [1]. Some of them, like this one, are more Ruby specific, others are RubyGems specific [2].
>
> If you go through this patch, you'll see that this patch is definitely Ruby specific. It allows to install RubyGems into dedicated directory (specifiable by configuration parameter) and extends Ruby's search path to include this path.
>
> There might be also required patch to RubyGems's setup.rb to allow to install updated RubyGems into this location, but first, I'd like to see this feature accepted.
>
> Please note that this feature is just optional and it keeps the current Ruby+RubyGems behavior intact unless requested.

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.