installerTool implemented

README.md

@@ -379,13 +379,17 @@ Depending on the application or pkg there are a few more variables you can or ne
 
 - `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 the folder of this binary, and it will be called like this:
+  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 `installerTool` for the installer app (if named differently that `name`. Installomator will add the path to the folder/disk image with the binary, and it will be called like this:
      `$CLIInstaller $CLIArguments`
-  So for most installations `CLIInstaller` should contain the `appName` for the CLI call (if it’s the same).
+  For most installations `CLIInstaller` should contain the `installerTool` for the CLI call (if it’s the same).
   We can support a whole range of other software titles by implementing this.
   See label adobecreativeclouddesktop.
 
+- `installerTool`:
+  Introduced as part of `CLIInstaller`. If the installer in the DMG or ZIP is named differently than the installed app, then this variable can be used to name the installer that should be located after mounting/expanding the downloaded archive.
+  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: