Comment #3 on issue 30730 by [email protected]: KeystoneRegistration
1.0.7.1306 tag path and tag key
http://code.google.com/p/chromium/issues/detail?id=30730
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=35030
------------------------------------------------------------------------
r35030 | [email protected] | 2009-12-18 18:09:40 -0800 (Fri, 18 Dec 2009) |
21 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/keystone_glue.mm?r1=35030&r2=35029
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/chrome.gyp?r1=35030&r2=35029
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/tools/build/mac/keystone_install.sh?r1=35030&r2=35029
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/tools/build/mac/keystone_install_test.sh?r1=35030&r2=35029
Adapt Chrome to use KeystoneRegistration 1.0.7.1306. Use "tag path"
and "tag
key" to direct Keystone to use a tag stored in the application as opposed to
in its ticket.
BUG=30730
TEST= - ksadmin --print-ticket --productid com.google.Chrome should show
tagPath pointing to GC.app/Contents/Info.plist, and
tagKey of KSChannelID;
- ksadmin --print-tag --productid com.google.Chrome should show the
value of the KSChannelID key in GC.app/Contents/Info.plist;
this should be the tag that is used for auto-updates
The above steps should be validated after the following operations:
- launching Chrome when on a user ticket,
- promoting Chrome from a user ticket to a system ticket, and
- when a Chrome update is applied (using this version of
keystone_install.sh) when on either a user or a system ticket.
The tagPath and tagKey will NOT be set when launching Chrome on a
system (promoted) ticket, but they WILL be set when the ticket is
initially promoted and also when an update is applied using this
version
of keystone_install.sh.
Review URL: http://codereview.chromium.org/506061
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
