-
Notifications
You must be signed in to change notification settings - Fork 168
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
Revisit uninstallers #642
Comments
A viable path for Linux and MacOS uninstallers could be to add that feature to Essentially, it could try and remove the base environment using default |
I just found that the uninstaller won't remove shortcuts for packages created in a new environment on Windows since the uninstaller doesn't know about theses prefixes. The solution here is to remove them for each environment it can find, but recursive searches in NSIS aren't ideal. Python/conda-standalone using pathlib's glob functionality would be a much better tool. |
Aren't we doing |
We only do This does not account for user-created environments. |
Checklist
What is the idea?
Research the best way to implement uninstallers. Currently, only Windows provides some, and they do not do all tasks in the conda-canonical way:
AutoRun
registry entry #572)~/.conda/environments.txt
The uninstallation logic is not present on Linux or macOS either.
Why is this needed?
Better uninstallation processes.
What should happen?
The system should be left in a functional state, with no lingering files or configuration.
Additional Context
Uninstallation times have been previously reported as slow, so we might need to balance speed and correctness. See #168. It's mostly UI related, so as long as the output is kept in check, we should be ok. Nevertheless, timings should be analyzed.
The text was updated successfully, but these errors were encountered: