summaryrefslogtreecommitdiffstats
path: root/chrome/tools/build/mac/FILES-official
diff options
context:
space:
mode:
authormark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-10-13 20:14:52 +0000
committermark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-10-13 20:14:52 +0000
commit4eeb018cc6f4b3a1d6715facaa3a3c54a22b4951 (patch)
tree6d37b0fdf811639f8657d74280609bf85d75ac10 /chrome/tools/build/mac/FILES-official
parentf5c172084ebace23f2c639a4d08cb13a98a0d336 (diff)
downloadchromium_src-4eeb018cc6f4b3a1d6715facaa3a3c54a22b4951.zip
chromium_src-4eeb018cc6f4b3a1d6715facaa3a3c54a22b4951.tar.gz
chromium_src-4eeb018cc6f4b3a1d6715facaa3a3c54a22b4951.tar.bz2
Put the Keystone installation script and codesign driver script next to the
.app bundle, and make them available to the packaging system. This ensures that the packager uses the correct logic to sign a bundle, and places the correct Keystone auto-update script into the package. Because things may move around in the bundle and the proper codesign invocation may change between versions, it is correct to store the codesign logic with the package being signed. Similarly, because the correct way to perform an client-side auto-update may change between versions, it is correct to store the auto-update script with the code. BUG=14610 (in support of unbreaking auto-update) TEST=none Review URL: http://codereview.chromium.org/261048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@28871 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/tools/build/mac/FILES-official')
-rw-r--r--chrome/tools/build/mac/FILES-official1
1 files changed, 1 insertions, 0 deletions
diff --git a/chrome/tools/build/mac/FILES-official b/chrome/tools/build/mac/FILES-official
index fd80032..2d3802c6 100644
--- a/chrome/tools/build/mac/FILES-official
+++ b/chrome/tools/build/mac/FILES-official
@@ -1 +1,2 @@
Google Chrome.app
+Google Chrome Packaging