OS X Blender updates overwrite existing installations
Posted: Tue Mar 10, 2015 8:31 pm
Can the update process for OS X be fixed so that the installer either creates a new directory, or asks the user where they want to install the update to?
Currently the installer automatically overwrites every instance of Blender on my machine. This is a problematic since I do not want my regular install of Blender to be overwritten. I also like to have multiple versions of Blender Octane available in the event an update has issues.
In order to prevent my previous Octane Blender and regular Blender executables from being overwritten, I must either move them to a new volume and unmount that volume, or copy them into a zip archive or unmounted DMG. Now that we're getting a more frequent rate of updates
such behavior is quite inconvenient 
.
NOTE that at the very least the current install behavior should be indicated with the other install info. The first time I updated it took me a while to realize where the application was placed, as it simply overwrote the older files but did not change the directory name. I was also completely unaware at the time that it overwrote my regular Blender executable as well. For new users this can be very confusing.
Currently the installer automatically overwrites every instance of Blender on my machine. This is a problematic since I do not want my regular install of Blender to be overwritten. I also like to have multiple versions of Blender Octane available in the event an update has issues.
In order to prevent my previous Octane Blender and regular Blender executables from being overwritten, I must either move them to a new volume and unmount that volume, or copy them into a zip archive or unmounted DMG. Now that we're getting a more frequent rate of updates
such behavior is quite inconvenient .NOTE that at the very least the current install behavior should be indicated with the other install info. The first time I updated it took me a while to realize where the application was placed, as it simply overwrote the older files but did not change the directory name. I was also completely unaware at the time that it overwrote my regular Blender executable as well. For new users this can be very confusing.