Table of Contents
Advertisement
Exporting a Single Package
ConflictManager Reference
Export and recompile
In order for you to export a package:
The original package installation must exist. The export process cannot create a new
installation.
The source files in the original installation and any files you added during conflict
resolution must have valid source paths.
The Prevent Package Export check box on the Package Attributes dialog box must
not be marked.
You cannot export:
Packages that are marked as read-only on the Package Attributes dialog box in
Software Manager.
Certain types of packages.
See
Restrictions on Resolving and Exporting Package Types
After you resolve conflicts for a package, you can export the changes to the original
Windows Installer or WiseScript installation, which you then recompile in Windows
Installer Editor or WiseScript Editor.
To export a single package
1.
(Enterprise Management Server only.) If multiple databases are open, select a
database in the Applications/Packages pane.
2.
Select Packages menu > Export.
The Export Package dialog box appears.
3.
Complete the dialog box:
Application Name
Select the application to export.
Package Name
Select the package to export.
Installation File
Specify the path and file name of the Windows Installer installation (.WSI or
.MSI) or WiseScript (.WSE) to export to. Normally, you should accept the
default, which is the file that was originally imported into Software Manager. If
you are exporting a WiseScript, you can export to a different file. You must
export to the same type of file that was originally imported.
The remaining options are different depending on the type of file you are exporting.
4.
If you are exporting a WiseScript, select one of the following:
Export changes for all packages whose conflicts have
been resolved. You also can have the installations
recompiled automatically after exporting.
See
Exporting and Recompiling Packages
Conflict Detection and Resolution
on page 47.
on page 44.
46
Advertisement
Table of Contents
