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

RVM plugin: use latest rubies #1073

Closed
wants to merge 1 commit into from
Closed

RVM plugin: use latest rubies #1073

wants to merge 1 commit into from

Conversation

jrhorn424
Copy link

These variables are hard-coded into the RVM plugin. They are updated to refer to the latest ruby patches available.

These variables are hard-coded into the RVM plugin. They are updated to refer to the latest ruby patches available.
@padde
Copy link

padde commented May 6, 2012

Wouldn't it make more sense to automatically find the latest ruby 1.8 / 1.9 with something like rvm list | grep ruby-1.8 | sed -E 's/^.*ruby-(.*)\[.*$/\1/g' | tail -n1 ?

@jrhorn424
Copy link
Author

That would work. My script-fu is weak. I have an edge-case already. I installed a performance patch of 1.9 when I was playing with debugger, but it's largely obsolete now that someone else has picked up the project and made it work with stable 1.9.

jrhorn424 at hook in ~
$ rvm list | grep ruby-1.9 | sed -E 's/^.*ruby-(.*)\[.*$/\1/g' | tail -n1
1.9.3-p125-perf 

@padde
Copy link

padde commented May 23, 2012

I don't see where the problem is with the performance patch. Could you be more specific?

@jrhorn424
Copy link
Author

Ah, sorry. It isn't my default ruby, and it isn't even the preferred patch I'd like to use of all the 1.9's. I don't know how trivial it would be to make the choice of rubies interactive. Perhaps it's better to just use whatever ruby is designated as default.

@robbyrussell
Copy link
Member

Have a more recent version now. Thanks

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

Successfully merging this pull request may close these issues.

None yet

3 participants