Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GEM_HOME and GEM_PATH not set by Rubyinstaller, is this default behavior? #319

Closed
illtellyoulater opened this issue May 2, 2016 · 1 comment

Comments

@illtellyoulater
Copy link

Hi, on Windows 7 64bit I am observing that after installing Ruby 2.3.0 64bit, using latest RubyInstaller, GEM_PATH and GEM_HOME env. variables are not set and this is giving me some problems with SSL root certificate file and other minor issues. Now, I know that I can easily set those vars manually, but what I am trying to understand here is if there is some kind of bug in RubyInstaller which prevents it to set them, in case this is the default expected behavior.

So, is RubyInstaller setting those environment variables (and possibly others) by default?
Based on this answer I will have to diagnose other kinds of problems with my system (where I also have installed JRuby 9.0.0.0. which is also in path...).
Thanks.

@Azolo
Copy link
Member

Azolo commented May 30, 2016

No, GEM_HOME and GEM_PATH are managed by Ruby itself unless explicitly asked to do so otherwise.

We considered at one point using GEM_HOME and GEM_PATH to install gems npm style in a different directory, but since binary gems are super common and have breaking changes in every minor release we decided against it.

@Azolo Azolo closed this as completed May 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants