Trevor Brown

Not sure. I don't know that asdf-ruby or ruby-build (which it asdf-ruby uses) have gotten much use on Big Sur yet.

For the asdf-erlang plugin we are moving away from strictly requiring homebrew to be installed to just asserting that the dependencies are present. That's another thing that should probably be...

@kamidev yep, just came across that issue with 1.8 RC1.

I do not think #29 fixed this issue.

Strange. Does `asdf reshim` fix this? What happens if you only run `asdf reshim` and don't install bundler?

@quintrino thanks for reporting. I believe the original intent of this code was to download the `$RUBY_BUILD_VERSION` version of ruby-build when the currently downloaded version doesn't match `$RUBY_BUILD_VERSION`. This should...

Also, just FYI ruby-build uses dates for the tag names, so when you see a date you are actually seeing the tag name.

@quintrino I see the bug. We check the commit sha against the output of `ruby-build --version`. My guess is that when we use a commit hash instead of a tag...

Some plugins strategically call the `reshim` command at certain times, like https://github.com/asdf-vm/asdf-nodejs/blob/master/bin/postinstall. But for most plugins it's best just to run `reshim` when you need to.

We encounter this with asdf-erlang too https://github.com/asdf-vm/asdf-erlang/issues/143