577
edits
Changes
m
improved readability and fixed wrong word 'chain' that should have been 'include'
<packages>
<package
id="wpkg1example-package" name="Windows Packager sample 1Example Package" revision="1" reboot="false" priority="0">
<depends package-id="other-package" />
...
</source>
In this example the dependency 'depends' makes that the "other-package" is installed install right ''before'' the current package "wpkg1example-package".
== Chaining a package ==
By using '''chain''' you ''chain'' a package to the current package, meaning that if this package is installed, the other package also has to be installed but right ''after'' the current package.
'''Attention:''' a chained package might also be installed before the package chaining it. This might happen if the chained package is either already installed (possible by another dependency) or has higher priority than the package which references it by chain. If you need to ensure that a package is installed before another one please specify a dependency (see [[Depending on a package]])
<packages>
<package
id="wpkg1example-package" name="Windows Packager sample 1Example Package" revision="1" reboot="false" priority="0">
<chain package-id="other-package" />
...
</source>
In this example the 'chain ' makes that the "other-package" is installed install right ''after'' the current package "wpkg1example-package".
In fact it would be exactly the same if "other-package" would be depending on this package "wpkg1example-package". But with some packages it may be more logical and even more practical by chaining another package instead of being the other package's dependant.
For example if you have a package "Gimp" for the application "The Gimp" and a package "GimpHelp" containing the Help files of the application. And you want "GimpHelp" always installed together with "Gimp". The "GimpHelp" package depends on "Gimp" as it needs a Gimp installation before it can be installed, so you could use 'depend' in the "GimpHelp" package. But in this case it is more logical to 'chain' "GimpHelp" to "Gimp" as it will be "Gimp" that you would want to assign to a profile.
<packages>
<package
id="wpkg1example-package" name="Windows Packager sample 1Example Package" revision="1" reboot="false" priority="0">
<include package-id="other-package" />
...
</source>
In this example the chain 'include' makes that the "other-package" is also installed install if the current package "wpkg1example-package" is installed.
[[category:Documentation]]