This is the user manual for Chromium Updater.
[TOC]
installdataindex
is one of the install parameters that can be specified for
first installs on the command line or via the
metainstaller tag.
For example, here is a typical command line for the Updater on Windows:
UpdaterSetup.exe /install "appguid=YourAppID&appname=YourAppName&needsadmin=False&lang=en&installdataindex =verboselog"
In this case, the updater client sends the installdataindex
of verboselog
to
the update server.
The server retrieves the data corresponding to installdataindex=verboselog
and
returns it back to the updater client.
The updater client writes this data to a temporary file in the same directory as the application installer.
The updater client provides the temporary file as a parameter to the application installer.
Let's say, as shown above, that the update server responds with these example file contents:
{"logging":{"verbose":true}}
The updater client will now create a temporary file, say c:\my path\temporaryfile.dat
(assuming the application installer is running from
c:\my path\YesExe.exe
), with the following file contents:
\xEF\xBB\xBF{"logging":{"verbose":true}}
and then provide the file as a parameter to the application installer:
"c:\my path\YesExe.exe" --installerdata="c:\my path\temporaryfile.dat"
- Notice above that the temp file contents are prefixed with an UTF-8 Byte Order
Mark of
EF BB BF
. - For MSI installers, a property will passed to the installer:
INSTALLERDATA="pathtofile"
. - For exe-based installers, as shown above, a command line parameter will be
passed to the installer:
--installerdata="pathtofile"
. - For Mac installers, an environment variable will be set:
INSTALLERDATA="pathtofile"
. - Ownership of the temp file is the responsibility of the application installer. The updater will not delete this file.
- This installerdata is not persisted anywhere else, and it is not sent as a part of pings to the update server.