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

Does not actually cycle through all rubies on OSX #22

Open
claco opened this issue Jan 21, 2016 · 2 comments
Open

Does not actually cycle through all rubies on OSX #22

claco opened this issue Jan 21, 2016 · 2 comments

Comments

@claco
Copy link

claco commented Jan 21, 2016

I'm working on setting up my Ruby environment using Ansible on both OSX and Fedora.

For whatever reason, rbenv each on my OSX machine appears to cycle through the available rubies, but not actually shim them in. the all plugin works just dandy, but I'd prefer each frankly.

 → rbenv versions
* system (set by /Users/claco/.rbenv/version)
  2.2.4
  2.3.0

 → rbenv each -v ruby --version
===[2.2.4]==============================================================
ruby 2.0.0p645 (2015-04-13 revision 50299) [universal.x86_64-darwin15]

===[2.3.0]==============================================================
ruby 2.0.0p645 (2015-04-13 revision 50299) [universal.x86_64-darwin15]

 → rbenv all ruby --version
2.2.4>> ruby --version
ruby 2.2.4p230 (2015-12-16 revision 53155) [x86_64-darwin15]

2.3.0>> ruby --version
ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15]
@claco
Copy link
Author

claco commented Jan 21, 2016

Possibly related: rbenv/rbenv#121

@claco claco changed the title Does actually cycle through all rubies on OSX Does'nt actually cycle through all rubies on OSX Jan 21, 2016
@claco claco changed the title Does'nt actually cycle through all rubies on OSX Does not actually cycle through all rubies on OSX Jan 21, 2016
@mislav
Copy link
Member

mislav commented Jan 21, 2016

What's the status of PATH at the time when you invoke rbenv each? Is there a version of Ruby whose bin directory is already pushed to the front of the PATH? If so, you must remove it before proceeding. The issue that you referenced is a long-standing limitation of rbenv that shelling out from one Ruby version to another is not straightforward. This would affect rbenv each, too.

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