Configure system-level Chrome settings (i.e. install its shortcuts) immediately following self-dest…

chrome/installer/setup/uninstall.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 //
 // This file defines the methods useful for uninstalling Chrome.
 
 #include "chrome/installer/setup/uninstall.h"
 
 #include <windows.h>
 
@@ skipping 1252 matching lines @@
     VLOG(1) << "Uninstallation complete. Launching post-uninstall operations.";
     browser_dist->DoPostUninstallOperations(product_state->version(),
         backup_state_file, distribution_data);
   }
 
   // Try and delete the preserved local state once the post-install
   // operations are complete.
   if (!backup_state_file.empty())
     file_util::Delete(backup_state_file, false);
 
+  // Upon uninstalling user-level Chrome, install shortcuts to the system-level
+  // Chrome if it exists (in most such cases the user-level uninstall is a
+  // self-destruction).
+  if (product.is_chrome() && !installer_state.system_install()) {
+    const ProductState* system_level_product_state =
+        original_state.GetProductState(true, browser_dist->GetType());
+    if (system_level_product_state) {
+      FilePath system_chrome_path(GetChromeInstallPath(true, browser_dist));
+      HandleActiveSetupForBrowser(system_chrome_path, product, true);

[grt (UTC plus 2), 2012/11/16 04:32:32]

this will do active setup for whatever version of user-level chrome is being
uninstalled rather than the version of chrome installed at system-level.  this
seems fragile.  is this intended?

[gab, 2012/11/16 04:51:20]

True, the other option is to trigger the system-level's active setup command;
this is what I was going to do originally, but somehow the other setup wasn't
dying early and I couldn't figure out why, so I went the simple route instead in
this CL; now that I think about it and have played a little bit more with
LaunchProcess, I think it's because I wasn't launching the other setup out of
job and this setup would terminate almost immediately after and bring the other
one down with it (does that even make sense?).

For now this only installs shortcuts so it's fine, but I agree that it could
diverge over time.

+    }
+  }
+
   return ret;
 }
 
 }  // namespace installer