Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0, Справочник

Страница: 123 / 302

Wise Package Studio Reference 123
Wise Package Studio Tools
Package Definition
¾
Not available in Standard Edition.
A Wise package definition file defines what is needed to install a package. At a
minimum, this is a command line. However, it can also be the installation file itself,
additional command lines, or any file that needs to be installed. Having a package
definition file lets you use Group Distribution in Software Manager to prepare the
package for deployment.
Defining a package in Workbench
Create a package definition so you can install:
z
A package that you could not otherwise repackage or deploy. Examples:
„
A Setup.exe of unknown format and the command line to run it.
„
An installation that you cannot repackage because its license agreement
prohibits it.
„
A device driver (.INF) with its .CAB files and the command lines to run it.
„
An installation that is on one or more CDs (example: Microsoft Visual Studio
.NET). In the package definition, specify the installation file or files and the
command lines to run them.
z
A package that consists of one or more command lines without any files. Example:
Define a package that contains a command line that runs a shell command on the
destination computer.
Package Definition creates a package definition file (.WPF), which lists the files and
command lines that make up the package. The package definition file is saved in its own
subdirectory of the share point Projects directory. The files in the package definition are
saved in a Files subdirectory of the package definition’s project directory. This ensures
that all the files are in a shared location and are accessible when the package is
distributed.
Package Definition imports the package definition file or queues it for import into the
Software Manager database. When the package definition file is imported into the
Software Manager database, its resources are not imported and are not available for
conflict management. To associate the resources with the package after the package
definition is imported:
1. Use SetupCapture to capture the package installation as a Windows Installer file.
2. Import the Windows Installer file into the Software Manager database. During
import, select the application and package name of the package definition file and
clear the option to overwrite the package.
See Creating a Package Definition File on page 124.
Defining a package in Software Manager
In Software Manager, you can edit an existing package definition or create a new one.
Create a package definition in Software Manager when you need to:
z
Install a package that you could not otherwise repackage or deploy.
z
Add a file or files to a package that is already in the Software Manager database.