Feature Requests item #28943, was opened at 2011-02-21 22:19 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=28943&group_id=126
Category: `gem` commands Group: None Status: Open Resolution: None Priority: 3 Submitted By: Sven Schwyn (svoop) Assigned to: Nobody (None) Summary: GEMRC environment variable Initial Comment: There are now three ways to alter the gem configuration, I'd like to suggest adding one more as follows (by order of precedence): - gem --config-file + GEMRC - ~/.gemrc - /etc/gemrc To make the case, here's what I'd use this feature for: On a production server, different Rubies (e.g. MRI 1.8 and 1.9) are installed and thus the global /etc/gemrc has --format-executable set to prevent conflicts. However, every Rack application has it's own gemset (similar to how RVM does) and for these gems --no-format-executable should be used. When you cd into the context of the application, the GEMRC environment variable is automatically set (again, much like RVM does) which points to an application specific gemrc file. GEMRC="/var/www/www.myapp.com/config/gemrc" This feature might also come in handy on shared servers or to overrule ~/.gemrc. Or tools like RVM could use this feature to pass gem configurations. (The system Ruby reads /etc/gemrc with --ri --rdoc whereas the RVM Rubies read the gemrc from GEMRC with --no-ri --no-rdoc.) I can give it a shot and submit an implementation, but it'd prefer to discuss whether this feature is desirable and would be included before I do so. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=578&aid=28943&group_id=126 _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
