What makes this more confusing is that /Users/david-dev/homebrew/Caskroom/miniconda/base was created by me using brew install, and thus owned by me, so why is it asking for my password? I thought the whole philosophy of brew is to not ask for the password except for in the very beginning if I decide to go with the default prefix (in this case I did not). Users/david-dev/homebrew/Caskroom/miniconda/baseĭavid-dev is not in the sudoers file. This incident will be reported.”įull output: ~ % brew uninstall -cask miniconda What the heck? Why?Īnd to make things worse, after I typed in my password, it said I’m “is not in the sudoers file. Uninstalling Homebrew is very similar to the way it is installed. In this tutorial, Ill show you how to uninstall Homebrew. Anyway, uninstalling Homebrew is not difficult. Pascal at 11:31 Pascal yeah I noticed I have a lot of old versions stacked here too. Perhaps you need to do a clean install again or there is an other reason. You need to run brew cask uninstall -force before installing the new version if you do not want the old version to stay there. However, now I’m trying to brew uninstall -cask miniconda, and it asked for my password. However, there might come a moment that you want to fully uninstall it. I also installed miniconda without a problem with brew install -cask miniconda. I installed brew by simply untarring the git repo into my homedir.
(I also have access to an admin account, but I deliberately created a standard account to mess around with Brew). I’m using Homebrew on macOS with M1 pro, in a non-admin standard user account.
0 kommentar(er)
