I am on a new debian 11 box need to reinstall ruby 2.7 because the configuration is borked. Ruby and bash aren't playing nice to recognize my executable folder. The bash terminal isn't recognizing ruby gem aliases despite following the advice in the aforementioned stack overflow post. So I've decided to just uninstall and reinstall ruby itself, and this time around manage everything with rvm.

I ran an internal ruby uninstall the individual gem command itself using instructions from this post Uninstalling Ruby gems.

Then I ranapt-get remove --purge ruby ruby-dev but my ruby folders (such as /var/lib/gems/ and /usr/lib/ruby) and all of their contents, including installed gems, are still there!

lo and behold it hasn't been uninstalled after all! at least not in the way that i need to be. what can i do moving forward to remedy this issue?

EDIT : I remembered later that I had attempted just simply uninstalling the individual gem from my existing ruby installation. with $> sudo gem uninstall gemname -i /var/lib/gems/2.7.0/

i believe the problem lies in hanging or conflicting configuration files. due to the difference in the file locations when executing from a user or sudo environment.

CodePudding user response：

According to https://dontusesystemruby.com/#/ unless you're building a docker image you should not be using pre-installed system ruby or ruby installed from the default package manager. This site (https://dontusesystemruby.com/#/) gives myriad reasons for using rvm.

answer: install and compile ruby yourself with rvm. get it through curl with a gpg key from the mit keyserver (the others appear to be down). then reload the bashrc with . .bashrc