A story of PROMPT_COMMAND and RVM

#1

Post by mpapis » Mon, Dec 17, 2012, 1:34 PM UTC

A story of PROMPT_COMMAND and RVM
niczsoft.com

Re: A story of PROMPT_COMMAND and RVM

#2

Post by kawsper » Mon, Dec 17, 2012, 2:04 PM UTC

RVM can really bite you if you are not careful. And it can really mess things up https://github.com/wayneeseguin/rvm/issues/1234

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.

Re: A story of PROMPT_COMMAND and RVM

#3

Post by mpapis » Mon, Dec 17, 2012, 2:16 PM UTC

kawsper wrote: post #2

RVM can really bite you if you are not careful. And it can really mess things up https://github.com/wayneeseguin/rvm/issues/1234 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…

The issue you mention was a duplicate and was fixed already.

Re: A story of PROMPT_COMMAND and RVM

#4

Post by RegEx » Mon, Dec 17, 2012, 2:17 PM UTC

This post is 30% technical, 70% politics.

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.

[0]: https://github.com/sstephenson/rbenv

Re: A story of PROMPT_COMMAND and RVM

#5

Post by RegEx » Mon, Dec 17, 2012, 2:20 PM UTC

kawsper wrote: post #2

RVM can really bite you if you are not careful. And it can really mess things up https://github.com/wayneeseguin/rvm/issues/1234 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…

Do any of these behave like Python's virtualenv? I really like how virtualenv works, and if I ever want to get semi-serious with Ruby, I'd like to have something similar.

Re: A story of PROMPT_COMMAND and RVM

#6

Post by tamal » Mon, Dec 17, 2012, 2:33 PM UTC

RegEx wrote: post #4

This post is 30% technical, 70% politics. 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 di…

Probably why it's titled "A story…"

Re: A story of PROMPT_COMMAND and RVM

#7

Post by regularfry » Mon, Dec 17, 2012, 2:56 PM UTC

RegEx wrote: post #5

kawsper wrote: post #2

RVM can really bite you if you are not careful. And it can really mess things up https://github.com/wayneeseguin/rvm/issues/1234 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…

Do any of these behave like Python's virtualenv? I really like how virtualenv works, and if I ever want to get semi-serious with Ruby, I'd like to have something similar.

Not for managing the Ruby version itself, but I wrote gemenv (http://github.com/regularfry/gemenv) to be able to have the same style of contained package management that virtualenv offers. There's no reason you couldn't ./configure --prefix=gemenv and build a ruby binary into it as well.

Re: A story of PROMPT_COMMAND and RVM

#8

Post by themckman » Mon, Dec 17, 2012, 3:14 PM UTC

regularfry wrote: post #7

RegEx wrote: post #5

Earlier quoted context omitted.

Do any of these behave like Python's virtualenv? I really like how virtualenv works, and if I ever want to get semi-serious with Ruby, I'd like to have something similar.

Not for managing the Ruby version itself, but I wrote gemenv ( http://github.com/regularfry/gemenv ) to be able to have the same style of contained package management that virtualenv offers. There's no reason you couldn't ./configure --prefix=gemenv and build a ruby binary into it as well.

You can use virtualenv to manage the python version, also. If you have multiple versions of python installed, say python27 and python3, using the --python option of virtualenv you can tell it which executable you want to create the virtualenv with.

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.

Re: A story of PROMPT_COMMAND and RVM

#9

Post by mpapis » Mon, Dec 17, 2012, 3:19 PM UTC

regularfry wrote: post #7

RegEx wrote: post #5

Earlier quoted context omitted.

Do any of these behave like Python's virtualenv? I really like how virtualenv works, and if I ever want to get semi-serious with Ruby, I'd like to have something similar.

Not for managing the Ruby version itself, but I wrote gemenv ( http://github.com/regularfry/gemenv ) to be able to have the same style of contained package management that virtualenv offers. There's no reason you couldn't ./configure --prefix=gemenv and build a ruby binary into it as well.

thanks for mentioning - added to my list https://github.com/wayneeseguin/rvm/blob/master/help/alt.md

Re: A story of PROMPT_COMMAND and RVM

#10

Post by regularfry » Mon, Dec 17, 2012, 3:32 PM UTC

themckman wrote: post #8

regularfry wrote: post #7

Earlier quoted context omitted.

Not for managing the Ruby version itself, but I wrote gemenv ( http://github.com/regularfry/gemenv ) to be able to have the same style of contained package management that virtualenv offers. There's no reason you couldn't ./configure --prefix=gemenv and build a ruby binary into it as well.

You can use virtualenv to manage the python version, also. If you have multiple versions of python installed, say python27 and python3, using the --python option of virtualenv you can tell it which executable you want to create the virtualenv with. 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 a…

That's what I mean - I specifically wanted gemenv not to worry about installing rubies. It does one job, and one job only :-)