Before creating a product check that one of the following conditions is true:
A very important example is a parameter product. If you have defined client parameters and created a parameter product, and the program needs other than the default values preset in the package, you must always install the parameter product first on the target computers before the actual program can run properly. Therefore, you must define a dependency for the packaged product on the parameter product in the info.sxp file.
Another example is a desktop publishing program that requires specific fonts and printer drivers to produce the correct output. Although the fonts and printer drivers are not essential at installation time, they must be installed on the users' computers later and they must be defined as dependencies in the info.sxp file.
When you create a product with a dependency, you can use the negative dependency feature. That means you enter a product name and version preceded by the ! operator in the InternalDependence section of the info.sxp archive file. Consequently, that product must not be installed on the target computer if you want to install the package you have just finished packaging. This is a very useful feature to account for incompatibilities between specific products, a company's hard disk restrictions, or other company policies.
In contrast, if you want to specify a (positive) dependency, you can also choose to create a delta product instead of specifying a positive dependency.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|