asdf-vm / asdf-vm/asdf-ruby

Consider setting RUBY_BUILD_CACHE_PATH?

Open
#422 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
734
Forks
156
Avg merge
17h 6m
Merged PRs (30d)
1

Description

Hi there! I recently ran into some trouble installing ruby on a fedora vm, and in the process of resolving the build errors I ran `asdf install` several dozen times.

Every time I attempted to install ruby with asdf, it downloaded a new collection of artifacts into a timestamped folder. This slowed down my debugging process, and a handful of times in the process I ran into "no space on device" errors and found that the disk backing /tmp was full. Manually clearing out the cache is easy enough, but seems like it should be unnecessary.

I posted on [ruby-build](https://github.com/rbenv/ruby-build/discussions/2463) about the process and the maintainer there mentioned RUBY_BUILD_CACHE_PATH. A [quick search here](https://github.com/search?q=repo%3Aasdf-vm%2Fasdf-ruby%20RUBY_BUILD_CACHE_PATH&type=code) didn't turn anything up -- perhaps this would be an easy way to decrease the suffering of someone who is already fighting with the computer to get ruby installed?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.