Bump min PNaCl version to 14173.

chrome/browser/component_updater/pnacl/pnacl_component_installer.cc

Index: chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
diff --git a/chrome/browser/component_updater/pnacl/pnacl_component_installer.cc b/chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
index 2bb7518e22907ac08995eeb2871332077e52e7d5..d20f75e21882c6e1e3d50263d46df746365f57b9 100644
--- a/chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
+++ b/chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
@@ -65,7 +65,7 @@ void SetPnaclHash(CrxComponent* component) {
 
 // If we don't have Pnacl installed, this is the version we claim.
 const char kNullVersion[] = "0.0.0.0";
-const char kMinPnaclVersion[] = "0.1.0.13367";
+const char kMinPnaclVersion[] = "0.1.0.14173";

[Mark Seaborn, 2014/12/11 19:22:43]

As an aside, what happens when we switch to using Git instead of SVN for NaCl?

Will we need to invent a monotonically-increasing version number for this?

[jvoung (off chromium), 2014/12/11 19:58:39]

Yes, we will need to have some monotonically increasing version number.

This has follow the chrome extension manifests' version:
https://developer.chrome.com/extensions/manifest/version, I believe.

I had used the NaCl revision number as one of the components, and it would be
nice if there was something similar when we switch to Git to help identify the
version of the build but also work with this format.

 
 // Initially say that we do not need OnDemand updates. This should be
 // updated by CheckVersionCompatiblity(), before doing any URLRequests