REQUIRES
element specifies a package dependency.
This can only be specified in a
PCK
block and defines that the
package in which the REQUIRES
element appears depends on
another package to be installed.
This element is optional, but can appear more than once per PCK
block.
This element has no attributes.
Among others, a dependency has the following consequences:
REQUIRES
element comes in two flavors:
<REQUIRES>vendor\application\package\major\minor[\revision]</REQUIRES>
If a non-decimal string is specified, this works just as in the PACKAGEID
attribute (see Package IDs).
This is useful if a package in your product is an add-on to some other software which is
distributed in WarpIN archive format also. Of course, this requires that you know the
ID string of that package.
Note that in this context, the version substring
("major\minor[\revision]"
) is understood as
the minimum version of that package which is required for your package to
work. Any installed higher version will be accepted by WarpIN. (If you do not
require a specific version, specify "0\0\0"
, since any installed version
number will be higher than that.)
<REQUIRES>index</REQUIRES>
If a decimal number only is specified, this references the package
in the current archive with the index index
, which must exist.
Internally, this will then store the PACKAGEID
of that package as a
requirement, so this is just a shortcut so you don't have to retype those package IDs
all the time. You can, of course, also specify the package ID string of another package
in the archive instead.
SELECT=NODESELECT
attribute to the
PCK
element, the REQUIRES
element does store a dependency in the database, so always use this for
specifiying dependencies.