Table of Contents
Advertisement
Importing From the Share Point Directory
Software Manager Reference
included in the imported patch or transform package and changes how it behaves when
it is installed.
Example: Suppose that two different transforms can be applied to a base package.
The Base Package installs File A, File B, and File C.
Transform 1 deletes File C.
Transform 2 installs Registry Key X and modifies File C.
When you apply the transforms like
this:
Base Package
Transform 2
Base Package
Transform 1
Transform 2
See:
Importing a Windows Installer Patch File
Importing a Transform File
Package Groups
on page 41
When the Database pane displays a number of packages that are queued for import, use
the Import from share point directory option in the Import Wizard to import the
packages into the Software Manager database.
When a package is distributed to the share point directory, the package and its source
files are copied to several subdirectories of the share point directory, and a .QUE file is
created to represent the package that is waiting to be imported into the Software
Manager database.
When you successfully import a package from the share point directory, its .QUE file is
deleted and the package information is added to the Software Manager database. Paths
to the new source file locations are also updated in the package installation file, except
for Wise package definition files.
See
About .QUE Files
on page 29 and
Note
When you use either Windows Installer Editor or WiseScript Editor to add files to a
package that has already been distributed to the share point directory and imported, a
prompt appears asking if you want to add the new files to the share point directory. If
you do so, the .QUE file for that package is reset and you must re-import the package in
Software Manager. If you have already detected conflicts for that package, you must
also redo the conflict detection process.
To import a package from the share point directory
1.
If multiple databases are open, select a database in the Applications/Packages
pane.
Transform 2 does this during
installation:
installs Registry Key X
modifies File C
installs Registry Key X
File C is not present, because the state of
the Base Package has been changed by
applying Transform 1.
on page 36
on page 33
How Source Files Are Indexed
Importing Packages
on page 16.
27
Advertisement
Table of Contents
