Don't matter how many times I execute the command rv cache clean it will always find a file to remove.
This is happening because of shell integration. The command shell init calls shell env and that is loading Configs and calling best_ruby() method which finally calls discover_rubies_matching in cache_ruby and create this cache. So the cache will never be really empty because shell integration is executed always.
Some solutions:
- Apply a
--no-cache to all shell init scripts. This still will be copying the interpreter to a temporal folder.
- Why cache a ruby interpreter already installed? I was looking the code and I don't get why to cache it if I already have it installed in the system. Why not just point to that location? I mean, that is what finally happen.
Any other idea?
Don't matter how many times I execute the command
rv cache cleanit will always find a file to remove.This is happening because of shell integration. The command
shell initcallsshell envand that is loading Configs and callingbest_ruby()method which finally callsdiscover_rubies_matchingincache_rubyand create this cache. So the cache will never be really empty because shell integration is executed always.Some solutions:
--no-cacheto all shell init scripts. This still will be copying the interpreter to a temporal folder.Any other idea?