Bump min PNaCl version to 14173.

Bump min PNaCl version to 14173.

We are changing the interface between Chrome and one of
the PNaCl translator nexes so that it uses the NaCl IRT
more (which is a more stable interface). However, this
means that we are not testing the old interface between
Chrome and the PNaCl translator nexe anymore on the chrome
waterfall, so the old interface may get broken. Bump the
min PNaCl version to try and get more users onto using the
new nexe, which uses the newer interface.

The new nexe also brings in a PNaCl translator based on
LLVM 3.5, so having that match the SDK (using LLVM 3.5)
is better for debugging (developer-only unstable debug
metadata has changed between 3.4 and 3.5).

BUG= https://code.google.com/p/nativeclient/issues/detail?id=3914

Committed: https://crrev.com/4fc66d88e351e20fa0d55ec3a0308a31cce5870c
Cr-Commit-Position: refs/heads/master@{#308030}

[jvoung (off chromium), 2014-12-10 18:36:21]

jvoung@chromium.org changed reviewers:
+ cpu@chromium.org

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

mseaborn@chromium.org changed reviewers:
+ mseaborn@chromium.org

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

LGTM

https://codereview.chromium.org/789273002/diff/1/chrome/browser/component_upd...
File chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
(right):

https://codereview.chromium.org/789273002/diff/1/chrome/browser/component_upd...
chrome/browser/component_updater/pnacl/pnacl_component_installer.cc:68: const
char kMinPnaclVersion[] = "0.1.0.14173";
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]

https://codereview.chromium.org/789273002/diff/1/chrome/browser/component_upd...
File chrome/browser/component_updater/pnacl/pnacl_component_installer.cc
(right):

https://codereview.chromium.org/789273002/diff/1/chrome/browser/component_upd...
chrome/browser/component_updater/pnacl/pnacl_component_installer.cc:68: const
char kMinPnaclVersion[] = "0.1.0.14173";
On 2014/12/11 19:22:43, Mark Seaborn wrote:
> 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?

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.

[cpu_(ooo_6.6-7.5), 2014-12-11 20:11:23]

lgtm

[jvoung (off chromium), 2014-12-11 22:57:05]

The CQ bit was checked by jvoung@chromium.org

[commit-bot: I haz the power, 2014-12-11 23:11:03]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/789273002/1

[commit-bot: I haz the power, 2014-12-12 02:29:56]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-12-12 02:30:38]

Patchset 1 (id:??) landed as
https://crrev.com/4fc66d88e351e20fa0d55ec3a0308a31cce5870c
Cr-Commit-Position: refs/heads/master@{#308030}