there shout be a hint in the commandline and the README how to update the definitions.
i got this error:
muescha$ rbenv install 1.9.3-p327
ruby-build: definition not found: 1.9.3-p327
muescha$ ruby-build --definitions
1.8.6-p383
1.8.6-p420
1.8.7-p249
1.8.7-p302
1.8.7-p334
1.8.7-p352
1.8.7-p357
1.8.7-p358
1.8.7-p370
1.9.1-p378
1.9.2-p180
1.9.2-p290
1.9.2-p318
1.9.2-p320
1.9.3-dev
1.9.3-p0
1.9.3-p125
1.9.3-p194
1.9.3-preview1
1.9.3-rc1
2.0.0-dev
jruby-1.6.3
jruby-1.6.4
jruby-1.6.5
jruby-1.6.5.1
jruby-1.6.6
jruby-1.6.7
jruby-1.6.7.2
jruby-1.7.0-preview1
jruby-1.7.0-preview2
maglev-1.0.0
maglev-1.1.0-dev
rbx-1.2.4
rbx-2.0.0-dev
ree-1.8.6-2009.06
ree-1.8.7-2009.09
ree-1.8.7-2009.10
ree-1.8.7-2010.01
ree-1.8.7-2010.02
ree-1.8.7-2011.03
ree-1.8.7-2011.12
ree-1.8.7-2012.01
ree-1.8.7-2012.02
i tried this and get the defintions updated (thanks to hathaway ):
brew unlink ruby-build
brew install ruby-build
i dont tried it, but this way without brew looks very cryptic :-(
http://squarism.com/2012/02/27/upgrading-rbenv/
i think it would be better if rbenv install looks directly in the github repository for the current definitions without reinstalling?
I had to do the unlink/install for ruby-build too. Is this a bug?
same here
On OS X, I use Homebrew and an alias to do updates to rbenv and ruby-build:
alias rbu='brew upgrade rbenv; brew upgrade ruby-build'
If no updates are needed you see benign error messages, for example:
Error: rbenv-0.4.0 already installed
Error: ruby-build-20130227 already installed
With ruby-build installed as a plugin to rbenv, the homebrew re-install doesn't load new definitions so that rbenv can find them. To get new definitions I had to delete ~/.rbenv/plugins then follow the instructions to install ruby-build as a plugin for rbenv:
rm -rf ~/.rbenv/plugins/ruby-build git clone git://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-build
This is a great time waster. By the time I am getting around to installing another ruby, a few months have passed and I have forgotten the location and git incantation for updating the definitions (remembering to do brew uninstall brew install of ruby-build is not a better way).
Both rbenv and ruby-build need to coordinate a better way to update definitions, all of them, where ever they are located.
rbenv update definitions rbenv which ruby-build ruby-build update definitions
That would save everyone a lot of google time.
A useful techniques is to use brew upgrade ruby-build (note: _upgrade_ not
update.) I use utility functions for keeping up-to-date with brew, rbenv,
and ruby-build:
#.bashrc
function bud { brew update; brew doctor; }
function rbu { brew upgrade rbenv; brew upgrade ruby-build; }
function rbis { ruby-build --definitions; }
function rbs { rbenv -v; ruby-build --version; rbenv versions; ruby -v; }
Most days I'll run:
$ bud
Then I'll fix reported issues, if any. Then:
$ rbu
If I see that ruby-build was updated, then I'll run:
$ rbis
and eyeball it to see what changed. If I see a new definition that I want,
I'll install it.
Hope this helps.
On Fri, Apr 12, 2013 at 10:28 AM, Robb Lovell [email protected]:
With ruby-build installed as a plugin to rbenv, the homebrew re-install
doesn't load new definitions so that rbenv can find them. To get new
definitions I had to delete ~/.rbenv/plugins then follow the instructions
to install ruby-build as a plugin for rbenv:rm -rf ~/.rbenv/plugins/ruby-build
git clone git://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-buildThis is a great time waster. By the time I am getting around to installing
another ruby, a few months have passed and I have forgotten the location
and git incantation for updating the definitions (remembering to do brew
uninstall brew install of ruby-build is not a better way).Both rbenv and ruby-build need to coordinate a better way to update
definitions, all of them, where ever they are located.rbenv update definitions
rbenv which ruby-build
ruby-build update definitionsThat would save everyone a lot of google time.
—
Reply to this email directly or view it on GitHubhttps://github.com/sstephenson/ruby-build/issues/254#issuecomment-16306018
.
This solution worked perfectly for me:
http://hathaway.cc/2012/07/how-to-get-the-latest-ruby-versions-for-rbenvruby-build/
If people used a package manager to install ruby-build, they should upgrade using the same package manager. If they cloned it via git, they need to do a git pull. We might have better instructions for this in the future, but for now, this is what we've stuck with. There are upgrade instructions in the official wiki.
Most helpful comment
With ruby-build installed as a plugin to rbenv, the homebrew re-install doesn't load new definitions so that rbenv can find them. To get new definitions I had to delete ~/.rbenv/plugins then follow the instructions to install ruby-build as a plugin for rbenv:
This is a great time waster. By the time I am getting around to installing another ruby, a few months have passed and I have forgotten the location and git incantation for updating the definitions (remembering to do brew uninstall brew install of ruby-build is not a better way).
Both rbenv and ruby-build need to coordinate a better way to update definitions, all of them, where ever they are located.
That would save everyone a lot of google time.