Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference page 121

Software Manager Reference
See About Patch and Transform Import
You cannot create cyclic dependencies. Example: If package A depends on Package B,
then you cannot make Package B depend on Package A.
With Enterprise Management Server, Security Setup determines whether you can edit
package relationship properties.
To create and edit package relationships
1. (Enterprise Management Server only.) If multiple databases are open, select a
database in the Applications/Packages pane.
2. In the Applications/Packages pane, click a package.
3. Select Packages menu > Relationships.
The Package Relationship dialog box appears.
4. On the Dependencies tab, do one of the following:
To add a dependency, click Add. On the Select Package dialog box, select a
package to add and click OK.
To edit a dependency, select a package and click Details. You cannot edit
subdependencies.
The Package Relationship Details dialog box appears.
5. Complete the dialog box:
Dependency
Define what should happen to the dependency if the dependent package is
installed:
Required Dependency (must precede)
The dependency must be installed before the dependent package. Example:
An .MSI is a required dependency for an .MST.
Optional Dependency (optionally precedes)
During Group Distribution, you have the option to include the dependency. If
you choose to do so, the dependency is installed before the dependent
package.
Supersedes
The dependency replaces the dependent package. (Example: If you have
two versions of the same package, you would make the latest version a
dependency that supersedes the earlier version). Association options are not
available for this type of relationship.
When a package has a supersedence relationship, you must specify whether
the package will be superseded. You do this in the Superseding Packages
dialog box, either when you add the package to a group or when you
distribute the group.
See Selecting Superseding Packages
Association
Define what should happen to the dependent package if the dependency is
installed:
None
The dependent package is not installed with the dependency.
Preparing Packages for Deployment
on page 36.
on page 89.
121