Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

Packaging In Place
If you set the package_in_place option to true, swpackage packages each of the specified
products such that the source files are not copied into the target depot. Instead, swpackage inserts
references to the source files that make up the contents of each fileset. Control scripts are always
copied.
This feature lets you package products in a development or test environment without consuming
the full disk space of copying all the source files into the target depot. Disk space analysis is skipped
when the package_in_place option is true.
The source files must remain in existence. If some are deleted, any operations that use the depot
as a source (for example, installing the product with swinstall) will fail when they try to access
the missing source files.
If a source file changes and the product is not repackaged, the information that describes the
source file will be incorrect (for example, the file checksum). This incorrect information will not
prevent the use of that target depot as a source (for example, installing with swinstall). However,
the incorrect information will be propagated along each time the product is copied or installed
from the depot. The result is that a swverify operation on the installed product always flags the
inconsistencies with an error unless you disable the check of file contents.
Following Symbolic Links in the Source
If you set the follow_symlinks option to true, swpackage follows every source file that is a
symbolic link and include the file it points to in the packaged fileset.
swpackage also follows each source directory that is a symbolic link, which affects the behavior
of the file * keyword (recursive file specification). Instead of including just the symbolic link in
the packaged fileset, the directory it points to and all files contained below it will be included in
the packaged fileset.
The default value for this option is false, which causes symbolic links that are encountered in the
source to be packaged as symbolic links. The symbolic link can point to a file that is also part of
the fileset, or to a file that is not.
Generating File Revisions
If you set the include_file_revisions option to true, swpackage examines each source file
using the what and ident commands to extract an SCCS or RCS revision value and assign it as
the file’s revision attribute.
Because a file can have multiple revision strings embedded within it, swpackage uses the first
one returned. It extracts the revision value from the full revision string and stores it.
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.
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.
198 Creating Software Packages