-
-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[APP] uninstall docker desktop that was installed with brew cask leaves symlinks #98
Comments
Hey, thanks for this. I'll take a look at this when I get a moment to see where the failure happens during cleanup. |
NP. thank you. great app by the way! here is another one that isn't completely gone
|
So from some testing I'm doing, it looks like the command fails on casks that require sudo to remove files. I'll keep playing with it and see, might need to separate the brew cleanup to just have it launch a terminal and run the commands from there automatically and the user can put in their password if needed. |
I think I have this working now. |
I am away from home for a few days. I will test as soon as I get back. thank you. |
No worries. |
Release this in latest version. |
I will be back home later this week and will test this. I will use the new release instead of beta. |
I finally got to trying this update. I did not try it on docker as I am afraid it would damage my orbstack installation. I tried it on aldente which requires a password on bre. It seems it worked correctly. If I see another app causing problems I will let you know. |
Awesome! And no problem, thanks for letting me know about this issue. |
I installed docker desktop using brew cask install.
Then I uninstalled with pearcleaner.
Brew showed it as still installed but with a bunch of broken symlinks.
brew cleanup did not help
but "brew uninstall --cask docker" afterwards fixed it.
App Details
Desktop (please complete the following information):
Additional context
pearcleaner has "homebrew cleanup is enabled" on
The text was updated successfully, but these errors were encountered: