rbenv migrations instructions don't work in a subtle way about asdf-ruby HOT 6 CLOSED

Either way the README does say this is possible, so I guess I need to figure out if I should remove that or figure out how to make this work with rbenv.

Great, thanks.

Yes, migrating may be painful, but let's don't say that it's possible in the README if we don't have a way to do this simple.

from asdf-ruby.

I want to add to this conversation because I vote for the rubies section being replaced in the README due to it being wrong. I ran the

mkdir ~/.asdf/installs/
mv ~/.rbenv/versions/* ~/.asdf/installs/ruby/

from the README and the output of gem environment was still using the .rbenv routes to reference gems despite shims being there to use the .asdf binaries. I had to run

asdf install ruby 2.4.2
asdf reshim ruby
gem install bundler

I found out that the values from gem environment were baked into the ruby build that the install performed. I'm not sure there will be a trustworthy way to just shim the versions from these other version managers. It's plausible that gems could be copied over, but it's probably not worth it by going through back channels like this just to be "compatible". I think understanding the legacy .ruby-version file is invaluable, but just copying over versions caused me, personally, some pain to figure out how to fix everything.

If the goal is to simplify the migration, then there probably is a way that the gems could be cached to have them be installed as part of the install process for a new ruby version, working kind of like the .default-gems file.

I hope this is helpful.

from asdf-ruby.

I confirm, output like this:

> gem list
/home/alex/.asdf/bin/private/asdf-exec: /home/alex/.asdf/installs/ruby/2.5.1/bin/gem: /home/alex/.rbenv/versions/2.5.1/bin/ruby: bad interpreter: No such file or directory
/home/alex/.asdf/bin/private/asdf-exec: line 52: /home/alex/.asdf/installs/ruby/2.5.1/bin/gem: Success

from asdf-ruby.

I honestly don't think it is wise to try to migrate all your Rubies from other Ruby version managers into asdf-ruby this way. It seems like there too many places for hard coded paths to hide to make it worth while. Ruby was compiled for that specific directory, and moving it is bound to create headaches.

Either way the README does say this is possible, so I guess I need to figure out if I should remove that or figure out how to make this work with rbenv.

from asdf-ruby.

Based on this discussion I've removed section in the readme on migrating rubies from other version managers. It will take longer to reinstall them, but it's easier than having to deal with rubies that contain hardcoded paths and cannot easily be migrated.

from asdf-ruby.

Based on this discussion I've removed section in the readme on migrating rubies from other version managers. It will take longer to reinstall them, but it's easier than having to deal with rubies that contain hardcoded paths and cannot easily be migrated.

OK, thank you.

from asdf-ruby.