Refactor chrome_launcher_support::GetAnyChromePath.

cloud_print/service/win/chrome_launcher.cc

Index: cloud_print/service/win/chrome_launcher.cc
diff --git a/cloud_print/service/win/chrome_launcher.cc b/cloud_print/service/win/chrome_launcher.cc
index 5dd876d30bef6b58fdde857f04c65a8fd2ca8339..9de123f71beec37d8782fffc9788193d874f6758 100644
--- a/cloud_print/service/win/chrome_launcher.cc
+++ b/cloud_print/service/win/chrome_launcher.cc
@@ -198,7 +198,8 @@ void ChromeLauncher::Run() {
 
   for (base::TimeDelta time_out = default_time_out;;
        time_out = std::min(time_out * 2, max_time_out)) {
-    base::FilePath chrome_path = chrome_launcher_support::GetAnyChromePath();
+    base::FilePath chrome_path =
+        chrome_launcher_support::GetAnyChromePath(false);

[Matt Giuca, 2014/10/30 02:54:50]

Question for Vitaly: Is there a reason why cloud_print is not getting the SxS
(canary) path for Canary builds? Is it not supported?

Maybe in the future this will make it easier to launch a Canary Chrome.

[grt (UTC plus 2), 2014/10/30 16:44:53]

The canary population is extremely small, and in most cases Canary can't be made
the default browser. I can see adding a fallback here to use canary if regular
Chrome isn't installed, but my gut tells me that non-canary should always be
preferred. The only exception to this would be if there's a very simple way to
determine that canary is actually the user's default browser when both are
installed. Since this is rarely the case, I wouldn't put a lot of effort into
coding it.

[Vitaly Buka (NO REVIEWS), 2014/10/30 16:46:17]

It's OK to try Canary first here and then fallback to regular one.

[Matt Giuca, 2015/01/09 06:17:32]

Echoing my statements in chrome_launcher_support.cc, I don't know why you would
want a canary cloud_print to use regular Chrome and vice versa.

Certainly the non-canary cloud_print should not be using canary Chrome. Why
would a canary cloud_print want to fall back to regular Chrome? (If you have
canary cloud_print, then surely you have canary Chrome installed.)

[grt (UTC plus 2), 2015/01/09 17:45:28]

Is the only path to installing canary cloud print via SxS Chrome? If the two are
intertwined, then yeah, launch canary from canary and regular from regular.

[Matt Giuca, 2015/01/12 06:54:26]

I don't know. Vitaly, can you answer this?

TBH I would prefer to keep the original functionality here (of launching the
regular Chrome only). This CL is a refactor, and should not be changing
functionality (especially since the author is completely unfamiliar with cloud
print). If indeed there is a bug here (canary cloud print only launches stable
Chrome), then that should have its own crbug and CL to fix.

[Vitaly Buka (NO REVIEWS), 2015/01/12 08:24:43]

sgtm.

There is no canary build of cloud print service and currently service always
uses non SxS Chrome. It would be nice to find a way to use SxS to testing or
troubleshooting, but you are right, it's a separate issue.

So lets keep just "false" here then.

On 2015/01/12 06:54:26, Matt Giuca wrote:

[grt (UTC plus 2), 2015/01/12 14:02:41]

SGTM

 
     if (!chrome_path.empty()) {
       CommandLine cmd(chrome_path);
@@ -258,7 +259,7 @@ std::string ChromeLauncher::CreateServiceStateFile(
     return std::string();
   }
 
-  base::FilePath chrome_path = chrome_launcher_support::GetAnyChromePath();
+  base::FilePath chrome_path = chrome_launcher_support::GetAnyChromePath(false);
   if (chrome_path.empty()) {
     LOG(ERROR) << "Can't find Chrome.";
     return std::string();