Hi,
This has been happening for the duration of the beta program I think.
If you do an uninstall of both client and repository on a OSX 10.7 machine, then some trace of Deadline v6 stays behind. Various shortcuts, etc…
Could do with tidying up a bit
Mike
Hey Mike,
Are you just referring to stuff in the Deadline6 and DeadlineRepository6 installation folders? Or is there other stuff that’s getting missed as well?
One thing we’re currently not doing is forcing the deletion of these folders if they contain files that weren’t put there by the installer. So after an auto-update, for example, the install folder will contain new files that the uninstaller will skip over.
We’re still on the fence with how to deal with this. In Deadline 5, the uninstaller would just force-delete the new files. However, on Linux for example, if you chose /usr/local as the installation folder, a forced uninstall would blow away the /usr/local/bin folder. We wanted to avoid the potential for that happening, but that means often leaving a bunch of stuff behind.
Thoughts?
Cheers,
- Ryan
Hi,
It was the application *.app short-cuts that I was referring to.
I was thinking that it should be safe to remove any of the local Thinkbox directories from a local install by the un-installer.
Even if I install some custom python packages, they should really be installed and deployed server side and then all slaves get the same setup deployed. If a user installs something local for testing, then consistency is broken and I would expect all files to be removed if the un-installer is run.
We work with the mindset, “if its worth keeping, then its on a backed up server” and if the only copy is on a local drive, then its either not worth keeping or just temp/RnD quick testy files.
It’s annoying having un-installers leave behind traces, but I also understand that un-installers are trying to be helpful.
Mike
Maybe what we’ll do is wipe all of our folders, but if someone picks an install folder like /usr or /usr/local for installation, we’ll either show a warning, or simply just not allow it.