Symantec CONFLICTMANAGER, Reference

Page: 45 / 54

ConflictManager Reference 45
Conflict Detection and Resolution
Package Export After Conflict Resolution
After you resolve conflicts, you must export the changes to the original Windows
Installer or WiseScript installation to produce an installation that does not conflict with
other packages on your organization’s computers.
You have the following options for exporting packages:
Group Policy Objects Conflicts between packages and Group Policy Objects are not typical
conflicts that you can resolve by changing files or registry keys, rather, they
are provided to inform you of packages that might override your group
policies.
Merge modules Changing a merge module affects all packages that use it. Instead, consider
adding the merge module to the package it conflicts with.
Microsoft hotfix Hotfixes typically are signed and cannot be changed. Alternative: Create a
WiseScript wrapper that installs the hotfix and then performs a post-
installation operation to install a changed source file.
Transforms If the transform was applied to a base package when it was imported, you
can resolve conflicts in and export the transform package. If the transform
was applied to a blank Windows Installer database, you cannot resolve
conflicts in or export the transform package.
Patches Patch files contain binary differences instead of full files. Alternatives:
z
Apply the patch during import of the base package. Then the patch’s
resources are added to the resources of the base package and you can
resolve conflicts for the base package.
z
Create a WiseScript wrapper that installs the patch and then performs a
post-installation operation to install a changed source file.
SOE Snapshots SOE Snapshot files are created solely to let you import a standard operating
environment into the Software Manager database. You cannot compile an
SOE snapshot file into an executable installation. Instead, change the
package that conflicts with an SOE Snapshot.
Subscribed packages that you
copied from another database by
package subscription You cannot change the source package files. Instead, change the packages
in your database.
InstallShield® Developer
installations that you imported
from an InstallShield executable Neither the original .EXE nor its embedded .MSIs can be edited.
Non-Windows Installer or non-
WiseScript installations that you
imported with the Universal
Import option The original installation file cannot be edited.
Export Export changes for a single package. After you export
the package you must compile it in Windows Installer
Editor or WiseScript Editor.
See Exporting a Single Package on page 46.