Symantec SOFTWARE MANAGER, Руководство по установке

Страница: 49 / 57

Software Manager Reference 49
Managing Packages
Warning
If you delete a package’s source files, you will never be able to recompile that
package because the source paths in the installation will refer to files that no longer
exist. Delete source files only when you are sure you will not need to compile the
package again.
5. Click OK.
The packages you selected are deleted from the database.
Changing the Package Status
Use Software Manager to maintain the status of packages in the Software Manager
database. The package status helps you determine whether a package is ready to be
deployed to end users.
In Windows Installer Editor, when you open an Available package from the Wise
Software Repository, you are prompted to change the status to Under Development.
To change the package status
1. If multiple databases are open, select a database in the Applications/Packages
pane.
2. In the Applications/Packages pane, click a package.
Information about that package appears in the Package pane.
3. If necessary, show the Package pane by selecting View menu > Application/Package
Summary
4. The Package pane displays one of these statuses in Package Status:
„
New
This status is assigned when the package meta data is added from within
Windows Installer Editor, but its resource information has not been imported. It
is also assigned when a Wise package definition file is imported from
Workbench.
You cannot change to or from this status manually. A New package is changed
to Under Development only when you use the Import Wizard to import its
resource information.
„
Under Development
The installation is still being developed.
You might need to check the package for conflicts and perform testing before
deploying it to end users. Packages are assigned this status when they are
imported to the Software Manager database.
„
Available
The package is ready for deployment or has been deployed. When you change a
package’s status to Available, the installation and its associated files are copied
to the Available Packages directory, and the installation file is set to read-only.
„
Retired
The package is no longer used in your organization.
Why should you keep an obsolete package in the Software Manager database?
When a legacy application that you no longer deploy is still in use in some