VMware PACKAGE MANAGER 1.1, Инструкция по установке и эксплуатации

Страница: 21 / 66

Using Package Studio to Create Software
Packages and Publish to Repositories
3
Using Package Studio to Create Software
Packages and Publish to Repositories
Package Studio is the application used to build software packages for installation on target Windows
servers and workstations.
Windows packages can include in-house and commercial software installation files, including .msi, .exe,
VBScripts, python, PowerShell.
To add a software installer to a package, it must be able to install and uninstall unmanned or quietly using
command line options, response files, or other similar methods.
About Package Naming and Versioning
The name and version assigned to a software package has significant impact on package management
when you are installing and uninstalling the package. When creating packages, you should have a clear
understanding of how package names and versions are used by the Package Manager when running
install and uninstall actions.
Managers of Windows software commonly work with installation files designed to install a specific
publisher-provided version; however, a software package usually contains much more. In addition to the
installation files, a software package can include command arguments, pre- and post-command scripts,
and an assigned software signing certificate, any of which can be modified to optimize the process or to
meet changing requirements. To account for all these variations in content, you must properly name and
version your software packages.
Correct Naming Practices
When, as a system administrator, you create a package to install an application, for example, SQL Server
2005, you will begin by creating a project (*.prj), and then configuring a package (*.crate file) that is
generated locally and can be published to a repository. The name of the project does not need to adhere to
the stricter naming conventions you should use for a published package. The name of the package is
determined by the value in the
Name text box located on the Properties tab.
When you are ready to make a package available by publishing it to a repository, carefully consider the
package name to ensure correct package management. The package name should not include the software
version. For example, you should name the package containing SQL Server 2005 (version 9.00.1399.06)
something like sqlserver, not sqlserver2k5. Instead, you should specify the primary version in the Version
field when you build the package in Package Studio. Additionally, you must specify the architecture on
which the package may be installed in the Architecture field. When the package is generated or published
using the recommended naming (sqlserver), with Version and Architecture specified in the required fields,
the file name is sqlserver_9.00.1399.06_x86.crate. Package Manager uses the specified version when
checking if a package is installed, when checking if a dependency is installed, and when uninstalling a
package.
VMware, Inc. 21