Attaching Solaris Software to Detected Listings

In this procedure, you learn how to attach a Solaris software to a name in the Components list under Local/Local PKGs. The name must already be in the Components list. Use this procedure to: replace a package with another one; manually upload a package; fix missing dependencies. See Table 5–1 for more explanations of when to use an attach procedure.

Console on Windows

If you are using a console on Microsoft Windows, this procedure is not applicable. See Adding Solaris Software with a Script, or delete an existing component (that you want to replace or fill), and use the scirpt to upload the new PKG.

Before You Begin

When you upload Solaris software, it must be in the form of a tar file, not a PKG.

1. Make sure the software is a directory of files, not a PKG.

2. Tar the directory:

   tar -cf name.tar /path/*

3. Copy the tarball to the console machine.

To Upload Solaris Software

1. Log in with full permissions or as the admin user.

2. From the drop-down list in the tool bar, select a distribution-architecture.

   The Components list shows the components relevant to your selection.

3. Select Local/Local PKGs/[category]/package group/package.

4. Do one of the following:

   • From the tool bar, click the Upload knowledge base File button.

   • Right-click the selected component and choose Local -> Upload.

   • From the Components menu, choose Local -> Upload.

     The Attach Target File window opens.

5. Check the relevant Solaris architecture-distribution.

6. In the Upload File From options, select Console.

7. Click the Select File button of the File Name field.

   The Choose RPM window opens.

   This window has the same name for both Linux (RPM) and Solaris (tarball).

8. Browse to and select the relevant package.

9. Click Open.

   The Choose RPM window closes, and the path name appears in the File Name field of the Attach Target File window.

10. Click Apply.

    The Status column indicates when the upload is done. The Local Expansion technology generates deployment rules for the new package.