Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference page 109

Software Manager Reference
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 manually
1. (Enterprise Management Server only.) 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.
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
Repackaging is still in progress.
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.
Note
If the package is under Revision Control, you must check it out before you can
change its status to Available. After changing the package's status to Available,
check the package back in, but be sure to clear the Reimport Package check
box on the Check In Package dialog box. You do not want to reimport a package
that you have just made available.
See Checking Packages Back Into Revision Control
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
limited cases, you need to ensure that new applications don't break the legacy
application.
Another reason is so that you can install the package on an as-needed basis
without having the original product CD. Example: Suppose an end user needs to
open a .PDF file created with version 3.0 of Adobe Acrobat, but for some
reason, the current version of Acrobat Reader cannot open the file. If the
Software Manager database contains Acrobat Reader 3.0, you can distribute the
package to the end user who needs it.
Managing Packages
on page 82.
109