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
rvm-shell path change in capistrano scripts #436
Comments
Your information is incorrect. RVM does not install rvm-shell to /usr/local/bin/ it installs it to /usr/local/rvm/bin/ ash shown below: ∴ ls /usr/local/rvm/bin/rvm ∴ rvm --version rvm 1.8.3 by Wayne E. Seguin (wayneeseguin@gmail.com) [https://rvm.beginrescueend.com/] |
counter proof: [root@devsys ~]# ls -al /usr/local/bin/rvm* And if you read that other thread, obviously other people have it do this too. |
It's been some time since I did this, so I don't know where this comes from, but /etc/rvmrc has:
grepping for rvm_prefix yields this suspicious line: true "${rvm_bin_path:="${rvm_prefix}/bin"}" which looks like it might be responsible for the wrong install path. |
The global rvmrc doesn't do what you're showing. it only contains umask g+w so thats a hand modified rvmrc. |
Ah, well, this has been installed for a while, so the rvmrc file is probably from the 1.6 series. I'm fairly sure I only used whatever the rvm website said to do at the time. I tried to update it today and the rvm update command was no longer valid that was in that version, so I ran the install script from the website again... it must have tripped on that old configuration. Perhaps the install script could put up a warning if it sees that? |
Another example where this must be causing pain: http://stackoverflow.com/questions/5253153/rvm-error-with-deploying-rails-app-via-capistrano |
As also reported to the capistrano folks in capistrano/capistrano#43, the capistrano recipe tries to use rvm-shell in /usr/local/rvm/bin, but they appear to now be installed in /usr/local/bin.
The temporary workaround that we found is to:
set :rvm_bin_path, "/usr/local/bin"
The text was updated successfully, but these errors were encountered: