Software Distributor Administrator Guide (September 2010)

This option is time consuming, especially when a what search fails and the ident
command is then executed.
The default value for this option is false, which causes swpackage to skip the
examination. No value for the revision attribute is assigned to the files being packaged.
10.6.9 Depots on Remote File Systems
Because the swpackage analysis and build phases operate as the superuser, there are
constraints on how swpackage creates, adds to, or modifies products on a depot that
exists in an NFS-mounted file system.
If the superuser does not have write permission on the remote file system, swpackage
will be unable to create a new depot-it will terminate before the analysis phase begins.
If the superuser does have write permission on the remote file system but the option
write_remote_files is false, swpackage will be unable to create a new depot - it
will terminate before the analysis phase begins.
If the superuser does have write permission on the remote file system and you set the
write_remote_files to true, swpackage creates the new depot and package
products into it.
The constraints for an existing NFS mounted depot are the same as when creating a
new depot.
So, you must:
1. Set the write_remote_files option to true and
2. Make sure the superuser can write to the NFS file system to package a depot on
an NFS-mounted file system.
When these constraints are satisfied, the ACL protection mechanism controls operations
on NFS mounted depots the same way it controls operations on local depots.
10.6.10 Verifying the Software Package
If swpackage created a depot rather than storing the package in an existing registered
depot, you must register the depot with the swreg command. (See “Registering Depots
Created by swpackage ” (page 260).)
After the depot is registered, you can verify it with the swverify command. For example,
to verify the integrity of the product Pascal in the local default depot:
swverify -d Pascal
For more information about verifying depots, see “Verifying a Depot (swverify -d) ”
(page 132).
You can also test the package by installing it on a system. For example, to install the
package named Pascal, located on the default depot /var/spool/sw in the host
svrhost, onto the primary root of a host named myhost:
swinstall -s svrhost Pascal @ myhost
266 Creating Software Packages