A story of PROMPT_COMMAND and RVM(niczsoft.com) |
A story of PROMPT_COMMAND and RVM(niczsoft.com) |
Right now I am looking for an alternative on my servers, because I need different Ruby versions across projects.
It is very interesting history following the development of RVM, to Rbenv and now also Chruby. It seems like 37signals is going the way of Rbenv.
It will be interesting to follow. It seems like a really fundamental problem, that need to be solved for us to build good software.
In the end, I found the trouble of running two reliable Ruby environments in production did not offset well against the cost of either updating applications to work with the same Ruby version, or running separate virtualized environments at the OS layer. The time spent debugging and updating our environment was too great in comparison to the additional cost of upgrading our software to all run on Ruby 1.9.
Assuming you're using rbenv and have all the correct paths.
Essentially, the author is upset that the author of rbenv[0] decided to criticize rvm instead of opening tickets and whatnot.
The author then goes on to blame the rbenv author for the year long delay in implementing PROMPT_COMMAND in rvm.
> We could have this code available for rvm users one year ago, possibly we could have a lot more of good solutions if the problems were discussed instead of throwing accusations as it was done by rbenv author.
Honestly I always felt the various multi-ruby helpers were a bit too much for me. I just compiled my rubies my self setting --prefix during configure and then would just adjust a few env variables to set up things like PATH and GEM_HOME and had no issues.