{
  "COMMENT": [
    "This file serves as a template for the resource info description used by ",
    "the NaCl Chrome plugin.  It is kept in the NaCl repository to prevent ",
    "hard-coding of NaCl-specific information inside the Chrome repository."],

  "abi-version": 1,
  "pnacl-llc-name": "pnacl-llc.nexe",
  "pnacl-ld-name": "ld.nexe"
}

{
  "COMMENT": [
    "This file serves as a template for the resource info description used by ",
    "the NaCl Chrome plugin.  It is kept in the NaCl repository to prevent ",
    "hard-coding of NaCl-specific information inside the Chrome repository."],

  "abi-version": 1,
  "pnacl-llc-name": "pnacl-llc.nexe",
  "pnacl-ld-name": "ld.nexe"
  "pnacl-sz-name": "pnacl-sz.nexe"
}

Add pnacl-sz entry to the pnacl_info.json.
Add pnacl-sz entry to the pnacl_info.json.

The file makes it so that Chrome doesn't really care what
we name our translator files. It only cares about the "key"
in this json file and the existence/name of this json
file. All the other tool filenames can change (the json
file indicates the new name and is distributed
along with the file whose name has changed).

Using component updater for PNaCl introduces some
version drift unless you bump the kMinPnaclVersion
in Chrome. This allows the drift so that we don't
need to bump the version for trivial stuff like
file renames.

To be used by work-in-progress-CL:
https://codereview.chromium.org/1005173006/diff/40001/components/nacl/renderer/plugin/pnacl_resources.cc
Rather than hard-code the pnacl-sz.nexe name on
the chrome side.

BUG= https://code.google.com/p/nativeclient/issues/detail?id=4091
R=kschimpf@google.com, stichnot@chromium.org

Review URL: https://codereview.chromium.org/1036013002
