[mini_installer] Remove code to delete files left behind by previous runs.
Once upon a time, mini_installer.exe created a directory in %TMP% in which to place files while it performed its work. Since it may fail to delete these files (e.g., due to crashes or interference by A/V software), it was given the power to delete files left behind by previous executions. This is all well and good, except that organic system-level installs did this work in a user's %TMP% directory rather than in the system's. Starting in r798844, mini_installer now puts its work directory next to itself. For installs driven by Google Update, GU will take care of (eventually) deleting anything left behind. Since this appears to be working reliably, we no longer need the %TMP% cleanup code. One caveat to this change is that files/dirs may once again accumulate in %TMP% if mini_installer is run from a directory in which it does not have write access. This will never be the case for proper Google Chrome installs. BUG=1125018 R=forshaw@chromium.org Change-Id: I50a768585d25ebdd508fc88f8036580a01bd8727 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2484651Reviewed-by:James Forshaw <forshaw@chromium.org> Commit-Queue: Greg Thompson <grt@chromium.org> Cr-Commit-Position: refs/heads/master@{#819537}
Showing
Please register or sign in to comment