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

Software Manager Reference
Detect file and resource conflicts between the merge module and other packages. It
also lets corporate developers manage and use the shared resources in merge
modules.
Add merge modules from the Software Manager database to installations in
Windows Installer Editor, if you mark Read Merge Modules List from Wise
Software Repository in Wise Options.
You cannot resolve conflicts in or export a merge module package, because changing a
merge module affects all packages that use the merge module. However, you can
change packages that conflict with the merge module. Typically, you do this outside
Software Manager, by removing the files and other resources included in the merge
module from the package, and adding the merge module to the package.
To import a merge module file
1. (Enterprise Management Server only.) If multiple databases are open, select a
database in the Applications/Packages pane.
2. Select Packages menu > Import.
The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify an .MSM or .WSM to import. Be sure to select the appropriate file
type from the Files of type drop-down list on the Open dialog box.
5. The following items become enabled:
Distribute source files to the share point directory
Mark this to copy all source files to a single, centralized location. Clear this
check box to import the package description into the Software Manager
database without copying its source files to the share point directory.
If you mark this check box, the source files are available so you can add a
merge module from the Software Manager database to an installation.
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the
same application and package names.
If you clear this check box and the application and package names are already
in the database:
If the existing package has resources, the new package is not imported.
If the existing package does not have resources, the new package's
resources are added to the existing package. An existing package might not
have resources if it consists only of a package definition.
Perform this operation on the Wise Package Studio server
If you are working on a client computer, mark this to perform this operation on
the Wise Package Studio server. You must use a UNC path to specify the
imported package. If the package and the Software Manager database reside on
the server, this significantly improves the performance of this operation for
large packages. With Enterprise Management Server, Security Setup
determines whether this option appears.
Add to Revision Control
Mark this to add the package to Revision Control during import.
Importing Packages
46