
Using Package Manager for Windows
6
Using Package Manager for Windows
Package Manager is the application installed on each machine to manage the installation and removal of
the software contained in packages. Package Manager is configured to use one or more repositories as
sources for packages.
The key components in the effective use of Package Manager is the proper creation of packages and
deploying the packages to repositories to which target machine has the necessary access.
Processing Dependencies
Working with packages, Package Manager is able to process the dependencies, Depends, Conflicts,
Provides, ensuring you do not install software on a machine that has negative results for the machine
users or affects the processes it runs.
For example, you have a machine where Package A is installed. You use Package Manager to install
Package B. The processing of the package includes checking the dependencies. In this example, Package B
is configured with a Conflicts with Package A. The installation does not proceed and the Package Manager
informs you of the conflict.
Security
As a standard security measure, Package Manager assumes that all packages must be signed with a private
key before they are installed or uninstalled. To accommodate organizations that do not use software
signing or where the immediate circumstances require you to ignore that signature, override options are
provided.
Add Repository Sources
A repository source is a section under a platform in a repository. Adding platforms and sections to the
repository allows you to control which repository sources the Package Manager for Windows uses when
installing and removing software. For example, a repository may contain platforms with both test sections
and release sections, but by making Package Manager aware of only the release sections, you ensure that
packages still in the testing phase are not added to the repository list and are therefore not available for
installation.
Additionally, you can add sources from more than one repository, and you can specify the order in which
the repository sources are queried.
The repository source list to which you are adding sources is repository.xml, located in C:\Documents
and Settings\All Users\Application Data\VMware\Wasp on each managed machine.
Prerequisites
The platforms and sections are defined in the repositories for which you are adding sources.
VMware, Inc. 49
Commentaires sur ces manuels