Ensure RBENV_DIR is an absolute path only if it was absolute to begin with #112
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I was hitting this issue too. Bundler would complain that the various gems were not installed despite being visible with "bundler list" and "gem list". |
|
How does RBENV_DIR control Bundler behavior? |
|
I came up with a workaround which supersedes this pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The recent rbenv updates are causing troubles for my
rbenv-bundlerplugin. I've isolated the problem to theabs_dirnamefunction, which is being (ab)used to convert relative pathnames to absolute ones. Unfortunately, that means absolute pathnames likeRBENV_DIR=/a/b/cget converted toRBENV_DIR=/a/b. I also made a change that prevents sourcing plugins twice by only expandingRBENV_HOOK_PATHonce.