Looking at the rubygems configuration file , I tried to hack gempath or gemhome to see if you can override (instead, just add to) the default values.
If, for example, the gempath installation should be empty or point to /dev/null , it prevents the use of system pearls, then this will be the way to go.
The main advantage of this, as I see it, is that your anti-rubygems configuration file can be passed to ruby ββ1.9 as a launch parameter (therefore not encoded), well documented and verified in your repository.
All this, of course, does not take into account that rubygems is part of the ruby ββ1.9 standard library - so ruby ββcan suffocate and die if he does not have access to his gems, depending on which part of the ruby ββbasic installation Requires gem functionality, YMMV.
source share