HP-UX Reference (11i v3 07/02) - 1M System Administration Commands N-Z (vol 4)

s
swmodify(1M) swmodify(1M)
NAME
swmodify - modify software products in a target root or depot
SYNOPSIS
swmodify [-d|-r][-p
][-u][-v][-V][-a attribute=[value]] [
-c catalog ][-C session_file ]
[
-f software_file ][
-P pathname_file ][-s product_specification_file|[
-S session_file ]
[
-x option=value ][-X option_file ][software_selections][
@ target_selection]
Remarks
For an overview of all SD commands, see the sd(5) man page by typing
man 5 sd on the command line.
DESCRIPTION
The
swmodify command modifies the definitions of software objects installed into a primary or alternate
root, or available from a software depot. It supports the following features:
• adding new objects - The user can add new bundles, products, subproducts, filesets, control files,
and files to existing objects (which will contain them).
• deleting existing objects - The user can delete existing bundles, products, subproducts, filesets, con-
trol files, and files from the objects which contain them.
• modifying attribute values - The user can add an attribute, delete an attribute, or change the exist-
ing value of an attribute for any existing object. When adding a new object, the user can at the
same time define attributes for it.
• committing software patches - The user can remove saved backup files, committing the software
patch.
With the exception of control files, swmodify does not manipulate the actual files that make up a product
(fileset). The command manipulates the catalog information which describes the files. However, swmo-
dify
can replace the contents of control files.
Common uses of swmodify include:
• adding file definitions to the existing list of file definitions in a fileset. Example: If a fileset’s con-
trol scripts add new files to the installed file system, the scripts can call
swmodify to "make a
record" of those new files.
• changing the values of existing attributes. Example: If a product provides a more complex
configuration process (beyond the SD configure script), that script can set the fileset’s state to
CONFIGURED upon successful execution.
• defining new objects. Example: to "import" the definition of an existing application that was not
installed by SD, construct a simple PSF describing the product. Then invoke
swmodify to load
the definition of the existing application into the IPD.
Options
swmodify supports the following options:
-d Perform modifications on a depot (not on a primary or alternate root). The given
target_selection must be a depot.
-p Preview a modify session without modifying anything within the target_selection.
-r Performs modifications on an alternate root directory, which must be specified in the @
target_selections option. (This option is not required for alternate root operations but is
maintained for backward compatibility. See the Alternate Root Directory and Depot Direc-
tory heading in sd(5) for more information.)
-u If no -a attribute=value options are specified, then delete the given software_selections from
within the given target_selection. This action deletes the definitions of the software objects
from the depot catalog or installed products database.
If -a attribute options are specified, then delete these attribute definitions from the given
software_selections (from within the given target_selection).
-v Turn on verbose output to stdout.
-V List the data model revisions that this command supports.
500 Hewlett-Packard Company − 1 − HP-UX 11i Version 3: February 2007