diff options
author | mark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-14 22:01:20 +0000 |
---|---|---|
committer | mark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-14 22:01:20 +0000 |
commit | 6b82c608d606fc848c3b0849204968e9e649ef86 (patch) | |
tree | 8c2b162bec717ef1bba6664997f98b23e6f215d6 /chrome/common/chrome_paths_mac.mm | |
parent | 30d425e79ececc49435b33cd017c97a08468da81 (diff) | |
download | chromium_src-6b82c608d606fc848c3b0849204968e9e649ef86.zip chromium_src-6b82c608d606fc848c3b0849204968e9e649ef86.tar.gz chromium_src-6b82c608d606fc848c3b0849204968e9e649ef86.tar.bz2 |
Official builds should be on the com.google.Chrome update product ID, not
com.google.Chrome.framework
BUG=24836
TEST=After running Google Chrome.app, run
~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/MacOS/ksadmin -p.
You should see, at the very least, tickets for com.google.Keystone and
com.google.Chrome, and they should appear to have valid data. You should
not see any tickets for com.google.Chrome.framework. If you run ksadmin
-l, you should not get any error output.
Review URL: http://codereview.chromium.org/273059
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29033 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/chrome_paths_mac.mm')
0 files changed, 0 insertions, 0 deletions