really install the requested version of bundler#24
really install the requested version of bundler#24palkan merged 2 commits intoevilmartians:masterfrom
Conversation
fixes evilmartians#23 Bundler won't uninstall because it is a 'default' gem and you won't end up running the version you added. Deleting the default gemspec first removes its protection. 'dip bundle -v' to check
palkan
left a comment
There was a problem hiding this comment.
👍 Thanks!
Just one minor comment.
| @@ -56,7 +56,9 @@ ENV LANG=C.UTF-8 \ | |||
|
|
|||
| # Upgrade RubyGems and install required Bundler version | |||
There was a problem hiding this comment.
Could you please add a link to this PR to the comment for clarification?
|
Thanks! |
|
I'm afraid it causes trouble, here's what I'm getting with this approach when trying to run And I am getting it when this exact bundler is installed and running the suggested command does not change a thing. I've "reverted" the changes this PR introduces and everything works well just as it was before. |
|
Fair enough....but strange...I am using this every single day, also with the refinement of only running it when I definitely need a specific version of bundler:
|
|
I reverted this and it works good for me just updating the system and installing the specific version |
The same for us: We had to revert this to get rspec to work in RubyMine again. (On the console using dip, rspec was already working fine.) |
|
BTW, since 2.3.0 it's simpler to deal with different versions - bundler will install it automatically. |
fixes #23
Bundler won't uninstall because it is a 'default' gem and you won't end up running the version you added. Deleting the default gemspec first removes its protection. 'dip bundle -v' to check