uninstallb could remove associated conda envs

[azazellochg]

to save disc space. At the moment it only deletes folders inside software/em, which are usually empty for many conda-based binaries
I'd imagine we could parse the env name from the activation command and then delete it (with user confirmation?)

[pconesa]

I think we need to provide some kind of "uninstallCommands"

[azazellochg]

i dont want to type "uninstallCommands", that's like 20 letters! :)

[pconesa]

I don't see other option.

[azazellochg]

you mean there's no way to know if a specific plugin has conda env installed or not?

[pconesa]

yes, unless we parse the commands and look for a conda create something which may not be robust enough?

[azazellochg]

we could check for ...ENV_ACTIVATION var, but it is also not very reliable. Maybe we could add another (boolean?) parameter to PluginInfo? I don't know if this class is used to store plugin properties..