It's not inherent to the core of ruby-build but is due to code meant to prevent ruby-build from deleting /usr/local or other sorts of FHS-compliant install locations, which TruffleRuby doesn't support: https://github.com/oracle/truffleruby/issues/1389
The problem with the existing method of detecting these installs is that it's too general and conflicts with the way asdf install works. This line is run to make the directory just before the plugin (which in this case is asdf-ruby which then calls ruby-build) gets to run. These install directories are a core part of how asdf (a set of bash scripts) tracks what's installed and what versions are available.
It seems to me that the check should explicitly be for FHS paths rather than just existing directories, or at least they should explicitly allow existing paths with .asdf as a component in the path.
eregon
commented
2 years ago
This is actually a
ruby-buildissue. It was introduced here: https://github.com/rbenv/ruby-build/pull/1784It's not inherent to the core of
ruby-buildbut is due to code meant to preventruby-buildfrom deleting/usr/localor other sorts of FHS-compliant install locations, which TruffleRuby doesn't support: https://github.com/oracle/truffleruby/issues/1389The problem with the existing method of detecting these installs is that it's too general and conflicts with the way
asdfinstall works. This line is run to make the directory just before the plugin (which in this case isasdf-rubywhich then callsruby-build) gets to run. These install directories are a core part of how asdf (a set of bash scripts) tracks what's installed and what versions are available.It seems to me that the check should explicitly be for FHS paths rather than just existing directories, or at least they should explicitly allow existing paths with
.asdfas a component in the path.Originally posted by @pinealservo in https://github.com/rbenv/ruby-build/discussions/1911#discussioncomment-2533456