Re: Keep all updates or only latest ones?
2015/09/12 15:07:12
(permalink)
The size of the updates do tend to increase over time but not by much. Generally, each installer is a complete version which overwrites the previous one. Rollback requires the previous installer. Instead of relying on rollback, however; I have created directories for each release of of the new SONAR. With every new release, I copy the SONAR Platinum folder to "SONAR Platinum-?" where ? is the release letter. So the current version exists in "SONAR Platinum" as the Windows default and I create a copy of the "SONAR Platinum" folder called "SONAR Platinum-H." This lets me review changes between versions without having the rollback/rollforward. It is not a complete solution as each release still rely on common "Shared" folders but I have found it to work for most cases. Each version requires approx 300MB. In time, I expect to move some of the releases offline but have plenty of space for now.
The only installers used in the new SONAR which have varied drastically in size are the Anderton Collection which included some release specific exclusive content. With the next release, the Anderton Collection installer would have the exclusive content removed and a new installer was added to user accounts for the content.
I would expect if any installer became unwieldy, Cakewalk would repackage it into multiple files.