Setting Up Env, Osx Rbenv and Bundle Battle

Setting up env, OSX rbenv and bundle battle

The problem seems to be that you're using a system ruby installed bundler, and not one installed with your rbenv ruby.

Run ruby --version to make sure your rbenv ruby is active, then run gem install bundler followed by rbenv rehash and then try reinstalling your gems and see if that works.

bundle exec spring not working with rbenv?

After a bit of exploration there seem there could be a couple of things in play here:

  1. system installed gems via bundler installed gems and the special behavior rails has
  2. generated binstubs at rvm and bundle level
  3. weird behavior in Spring 1.3.5

The root cause of the issue seems to be https://github.com/rails/spring/issues/295 which was fixed in 1.3.6. See: https://github.com/rails/spring/blob/master/CHANGELOG.md#136

Sadly, it turns out you cannot workaround this with the constraints the author specified in the question.

ruby: aliased to bundled_ruby

This is part of rbenv "magic" to handle several ruby versions with several gem versions. Have a look at ~/.rbenv/shims/ruby, IIRC the script is defined there.

If you want to disable this, just unalias ruby: this deletes the generated alias.



Related Topics



Leave a reply



Submit