These variables are called "automation" because WarpIN will not modify them, but only recognize them if they are set when WarpIN is started. As a result, if you set any of these variables before starting WarpIN, WarpIN will change its behavior during installation.
All these variables will be set in a CID script created on the "Configure" page during a regular WarpIN installation. As a result, you can do one regular WarpIN installation for an archive, save the CID script from the "Configure" page, and then use that CID script for subsequent installations to save time.
The following automation environment variables are currently defined:
SET WARPIN_DISPLAYPAGES={YES|NO}
If YES
is specified (which is the default), you get the regular installation
sequence with all the pages specified in the archive's install script (introduction,
readme, package selection etc., even though you may modify the default values with the
other variables below).
If NO
is specified, WarpIN will
jump directly to the installation process with no further chance for you to
interfere (except pressing the "Cancel" button).
Specify YES
first to test your installation variables. If you're
sure that everything works well, change it to NO
.
SET WARPIN_IGNOREDEPENDENCIES={YES|NO}
YES
to circumvent WarpIN's package dependency checks
(that is, checking for required packages as specified with the REQUIRES
attribute of the PCK element).
The default is NO
.
This is only meant as a last resort; normally, you should not disable
dependency checks.
SET WARPIN_SELECTPACKAGEx={INSTALL|DEINSTALL|IGNORE}
x
,
depending on the argument.
The default selection status is determined by the archive's author in the install script and depending on whether the package is already installed.
To select a package for installation, use INSTALL
. For de-installation,
use DEINSTALL
. To leave a package alone (that is, don't install if it's
not installed and don't de-installed if it's installed), specify IGNORE
.
WarpIN will terminate with an error message if the selection you specify here will
violate package dependencies (e.g. if you attempt to de-install a package which is
required by other packages), unless you also set
WARPIN_IGNOREDEPENDENCIES
to YES
(above).
Note that if the archive's author has specified the NODESELECT
attribute
with a PCK
tag, you can't deselect it with
this variable either.
SET WARPIN_TARGETPATHx=path
x
.
The default is specified in the archive's install script for package.
If you set the path for a package which has the BASE
attribute
set in its PCK
element, the other
paths are automatically updated.
SET WARPIN_UPDATECONFIGSYS={YES|NO}
YES
.
SET WARPIN_INSTALLWPSCLASSES={YES|NO}
YES
.
SET WARPIN_CREATEWPSOBJECTS={YES|NO}
YES
.
SET WARPIN_IFSAMEDATE={PROMPT|SKIP|OVERWRITE}
SET WARPIN_IFEXISTINGOLDER={PROMPT|SKIP|OVERWRITE}
SET WARPIN_IFEXISTINGNEWER={PROMPT|SKIP|OVERWRITE}
For each of them, the options have the following meaning:
PROMPT
: show the "File exists" dialog to have the user select
an action for this file.
SKIP
: skip the file, don't prompt.
OVERWRITEALL
: overwrite the file, don't prompt.
SET WARPIN_IFSAMEDATE=OVERWRITE SET WARPIN_IFEXISTINGOLDER=OVERWRITE SET WARPIN_IFEXISTINGNEWER=PROMPTThese defaults can be changed by the user in WarpIN's "Confirmations" dialog. However, specifying these environment variables will override the selections in that dialog.
SET WARPIN_LOGFILEPATH=path
path
must be the fully qualified file name of the
WarpIN log file (for example, C:\OS2\INSTALL\WARPIN.LOG
). The file
is created if it doesn't exist. If it exists, new entries are appended to the bottom.