1
edit
Changes
→Actions: download
==Actions==
Wpkg understands three several actions: '''install''', '''upgrade''' and , '''remove''' and '''download'''. Multiple commands for each of these actions can be listed in the config file and wpkg will execute them in the order they are listed.
The '''install''' commands are executed by wpkg when a new package comes into scope for a profile.
The '''remove''' commands are executed when a package is removed from a profile.
The '''download''' commands are always executed.
In many of the examples in the [[:Category:Silent_Installers]] section, cmd.exe is executed to perform environment variable expansion and to use 'start /wait' to wait on the command being executed. This method of executing commands results in cmd windows appearing on screen. However, this method does not appear to be necessary. The current version of wpkg (0.9.10) executes commands using the WScript.Shell.Exec() function, which should expand environment variables. This isn't explicitly stated in the Microsoft SDK documentation, but seems to be the case. Wpkg then waits until the command is completed before continuing.
<pre>
<download url='http://wpkg.example.com/installers/some.msi' target="installers\some.msi" />
<install cmd="msiexec /qn /i %SOFTWARE%\package.msi" />
<install cmd="msiexec /qn /i %SOFTWARE%\package.msi" timeout="1800" />
* delayed - reboot once the package action is complete and wpkg.xml is updated
* postponed - reboot once all the packages have been processed
Please note that the target value for a download action is always relative to the downloadDir defined in wpkg.js (and there's currently no configuration option to change this from the default of %TEMP%).
==Quick examples==