diff options
| author | tommi@chromium.org <tommi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-12-29 19:20:18 +0000 |
|---|---|---|
| committer | tommi@chromium.org <tommi@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-12-29 19:20:18 +0000 |
| commit | 57618d827ba3d4d618b78518f538c4c613bbd906 (patch) | |
| tree | 1d3a2608076bdfacadd1f0c13836e3d7be350e28 /chrome/app/nibs | |
| parent | 253274b4e2ffeea590480f461c6a0bdbfa5e4369 (diff) | |
| download | chromium_src-57618d827ba3d4d618b78518f538c4c613bbd906.zip chromium_src-57618d827ba3d4d618b78518f538c4c613bbd906.tar.gz chromium_src-57618d827ba3d4d618b78518f538c4c613bbd906.tar.bz2 | |
Do machine inspection on install.
When installing Chrome [x]or Chrome Frame in multi mode, check if the other product (CF xor Chrome) is installed.
If it is, also include it in the installation as we need to update both products in sync.
For Chrome Frame, I also added checks to see if CEEE is already enabled or if the user has already opted into GCF.
If CEEE has been enabled, we implicitly include it when the install is run even though ceee is not on the command line.
If ready-mode is set on the command line but Chrome Frame is already installed without it, we won't enable ready mode.
TEST=Try installing Chrome Frame in multi mode. Then install a more recent version of Chrome in multi mode. Both product should be updated. Secondly, for Chrome Frame, install it first and then try to run the installer again, but with ready-mode ont the command line. Chrome Frame should not be switched to ready mode.
BUG=61609
Review URL: http://codereview.chromium.org/6091008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@70268 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/app/nibs')
0 files changed, 0 insertions, 0 deletions