Limitations When Using the package Keyword

Note these limitations when using the package keyword:

• Some packages are required and cannot be deleted.

• You cannot individually add or delete localization packages by using the package profile keyword. To add localization packages, use the locale profile keyword.

• Packages cannot be retrieved from an FTP server location or local backup, such as tape.

• Packages within the Solaris distribution being installed cannot be added from alternate locations. If a package from the Solaris distribution is specified, the package cannot be followed by an alternative location in order to maintain consistency with the resulting installed system.

• In order to install without manual intervention, the package must be installable by using the pkgadd command. The same admin file must be used to install the software group packages and the package that resides in another location.

  • If the retrieval_type is HTTP, then the package must be in stream format.

  • If the retrieval_type is NFS server, local device, or local file, then the package should follow standard packaging format with the directory name being the same as the package being installed.

  • If a package is being added from a separate location and a package depends on another package that is not currently installed, the package is not installed. An error message is logged into the install or upgrade log file.

• If the package is being installed with a Solaris Flash archive, follow these guidelines.

  • Any package installed must be compatible with the archive.

  • If a package is present in the archive, the JumpStart overwrites the existing package.