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

Upgrade strategy should allow a specific version #98

Closed
cgriego opened this issue Apr 25, 2012 · 2 comments
Closed

Upgrade strategy should allow a specific version #98

cgriego opened this issue Apr 25, 2012 · 2 comments
Assignees

Comments

@cgriego
Copy link
Contributor

cgriego commented Apr 25, 2012

The upgrade_rvm helper only allows "latest" and "head as valid values, but the rvm get supports a wide variety of options.

Usage:

  rvm get {stable|latest|latest-x.y|x.y.z|head|master|branch|help} [--auto]

Options:

  stable      - install the latest RVM stable release

  latest      - install the latest RVM release

  latest-x.y  - install the latest RVM release matching the x.y* pattern

  x.y.z       - install a specific RVM release

  head        - install the latest RVM development version
  master

  --auto      - automatically update shell profile files.

  help        - Output this message.

Branches:

  branch <branch>
  branch /<branch>
  branch <repo>/
  branch <repo>/<branch>

  Defaults:

    branch: master
    repo:   wayneeseguin

  Examples:

    rvm get branch shoes   # will fetch branch shoes  from wayneeseguin/rvm repo
    rvm get branch mpapis/ # will fetch branch master from mpapis/rvm       repo

When using a specific version, it would be nice if the current version were detected and rvm were not reinstalled unnecessarily.

@fnichol
Copy link
Contributor

fnichol commented May 14, 2012

This should be less restrictive about install and upgrade options.

@ghost ghost assigned fnichol May 14, 2012
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants