Skip to content

Conversation

nporteschaikin
Copy link
Contributor

@nporteschaikin nporteschaikin commented Oct 13, 2016

...to use code's bundle, which may include rubocop extensions.

@wfleming
Copy link
Contributor

Doesn't setting this ENV var stop loading gems from the standard location?

@dblandin
Copy link
Contributor

Doesn't setting this ENV var stop loading gems from the standard location?

Nope. GEM_PATH adds entries in addition to the standard system location.

$ gem environment
  ...
  - GEM PATHS:
     - /usr/lib/ruby/gems/2.2.0
     - /home/app/.gem/ruby/2.2.0
  ...
$ export GEM_PATH=/code/vendor/bundle/ruby/2.2.0
$ gem environment
  ...
  - GEM PATHS:
     - /usr/lib/ruby/gems/2.2.0
     - /code/vendor/bundle/ruby/2.2.0
  ...

@wfleming
Copy link
Contributor

Cool, my bad. In that case LGTM, I think.

On Oct 13, 2016, at 19:25, Devon Blandin notifications@github.com wrote:

Doesn't setting this ENV var stop loading gems from the standard location?

Nope. GEM_PATH adds entries in addition to the standard system location.

$ gem environment
...

  • GEM PATHS:
    • /usr/lib/ruby/gems/2.2.0
    • /home/app/.gem/ruby/2.2.0
      ...
      $ export GEM_PATH=/code/vendor/bundle/ruby/2.2.0
      $ gem environment
      ...
  • GEM PATHS:
    • /usr/lib/ruby/gems/2.2.0
    • /code/vendor/bundle/ruby/2.2.0
      ...

      You are receiving this because you commented.
      Reply to this email directly, view it on GitHub, or mute the thread.

@nporteschaikin nporteschaikin merged commit 6eafacc into master Oct 14, 2016
@nporteschaikin nporteschaikin deleted the npc/gem-path-var branch October 14, 2016 15:26
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

Successfully merging this pull request may close these issues.

3 participants