Symantec CONFLICTMANAGER 8.0 - REFERENCE V1.0 Reference page 36

Conflict
Two files with the same name
have different hash values, or a
different version, date/time, or
size.
Two files with the same name
and the same hash value are
installed to the same directory,
but component GUIDs do not
match, and none of the
components are marked to be
permanently installed.
File is KeyPath to a component
in one package, but not in
another.
ConflictManager Reference
Problem
If the installation does not use
versioning rules (WiseScript
replacement options or the
Windows Installer
REINSTALLMODE property), the
older version can install over
the newer version, causing a
problem when each package
requires a specific version of the
file. Also, the new file might not
be compatible with the old one.
After both packages are
installed, uninstalling one of
them will remove the file,
breaking the remaining
package.
After both packages are
installed, uninstalling one of
them will remove the file,
breaking the remaining
package.
Conflict Detection and Resolution
Recommended resolution
Copy the file information (source path
included) from one package to another, or
isolate the file.
See Copying File Information
and Isolating Files on page 38.
Match GUIDs for identical files across
packages.
Resolve wizard:
Copy Up or Copy Down button
Rule action:
Replace the MSI component GUID with the
matching conflicting file's GUID
Or
Use the MSI component GUID in the active
package to replace the MSI component
GUID in the conflicting packages
Make both files KeyPaths to their respective
components.
Resolve wizard:
Fix Comp button
Rule action:
Use the MSI component KeyPath in the
active package to replace the MSI
component KeyPaths in the conflicting
packages
Or
Replace the MSI component KeyPath with
the matching conflicting file's KeyPath
on page 37
36