From 3ef4f1102534e73c59134765afce77f6fd793fbd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=B8ren=20Theilgaard?= Date: Wed, 10 Nov 2021 09:44:09 +0100 Subject: [PATCH] `CLIInstaller` and `CLIArguments` --- README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 2cfb90a..b90d9fd 100644 --- a/README.md +++ b/README.md @@ -372,11 +372,19 @@ Depending on the application or pkg there are a few more variables you can or ne `$updateTool $updateArguments` Will be run instead of of downloading and installing a complete new version. Use this when the `updateTool` does differential and optimized downloads. - e.g. `msupdate` (see microsoft installations) + e.g. `msupdate` (see various Microsoft installations). - `updateToolRunAsCurrentUser`: When this variable is set (any value), `$updateTool` will be run as the current user. Default is unset and +- `CLIInstaller`: +- `CLIArguments`: + If the downloaded dmg is actually an installer that we can call using CLI, we can use these two variables for what to call. + We need to define `name` for the installed app (to be version checked), as well as `appName` for the installer binary. So Installomator will add the path to this binary, and it will be called like this: + `$CLIInstaller $CLIArguments` + We can support a whole range of other software titles by implementing this. + See label adobecreativeclouddesktop. + ### Configuration from Arguments You can provide a configuration variable, such as `DEBUG` or `NOTIFY` as an argument in the form `VAR=value`. For example: