Previous Topic: Patch ProductsNext Topic: Conventions for Patch Packages


Main Patch Package

Consider the following scenario:

At the time the original PIF product, consisting of several packages, was installed, the customer decided to configure the installation of a certain subset of packages, that is, not all packages of the original product are installed at the customer side.

When a PIF patch product has to be installed in this scenario, it has to evaluate automatically which of its patch packages must be applied.

Therefore you must define a "main patch product" which serves as anchor for the individual patch packages, with appropriate dependencies to the individual patch packages.

The main patch package can be compiled as self-installing package, which ensures that the Installer will always be updated to the required version. Required patch packages are installed only if the original package for the patch exists. If an original package has not been installed on the target computer, the related patch is also not installed and no error is returned. The application of this patch package is ignored.

If the main patch package is removed (rolled back) all required individual patch packages are also removed (rolled back).