swmodify.1m (2012 03)

s
swmodify(1M) swmodify(1M)
The swmodify command supports the following syntax for each software_selection:
bundle
[.product[.subproduct][.
fileset]][,version]
product[.subproduct][.fileset
][,version]
• You can specify selections with the following shell wildcard and pattern-matching notations:
[], *, ?
• Bundles and subproducts are recursive. Bundles can contain other bundles and subproducts can
contain other subproducts .
• The
\* software specification selects all products. Use this specification with caution.
The
version component has the form:
[,r <op> revision][,a <op> arch
][,v <op> vendor]
[,c <op> category][,q=qualifier
][,l=location]
[,fr <op> revision][,fa <op> arch
]
• location applies only to installed software and refers to software installed to a location other
than the default product directory.
•
fr and fa apply only to filesets.
•
r , a , v , c , and l apply only to bundles and products. They are applied to the leftmost bun-
dle or product in a software specification.
• The <op> (relational operator) component can be of the form:
=, ==, >=, <=, <, >,or!=
which performs individual comparisons on dot-separated fields.
For example,
r>=B.10.00 chooses all revisions greater than or equal to B.10.00. The sys-
tem compares each dot-separated field to find matches.
• The
= (equals) relational operator lets you specify selections with the shell wildcard and
pattern-matching notations:
[], *, ?, !
For example, the expression r=1[01].* returns any revision in version 10 or version 11.
• All version components are repeatable within a single specification (for example,
r>=A.12,
r<A.20). If multiple components are used, the selection must match all components.
• Fully qualified software specs include the
r=, a=
, and v= version components even if they con-
tain empty strings. For installed software,
l= is also included.
• No space or tab characters are allowed in a software selection.
• The software instance_id can take the place of the version component. It has the form:
[instance_id]
within the context of an exported catalog, where instance_id is an integer that distinguishes ver-
sions of products and bundles with the same tag.
Target Selection
The swmodify command supports the specification of a single, local target_selection, using the syntax:
[ @/directory]
When operating on the primary root, no target_selection needs to be specified. (The target / is assumed.)
When operating on a software depot, the target_selection specifies the path to that depot. If the
-d
option is specified and no target_selection is specified, the default
distribution_target_directory is assumed (see below).
EXTERNAL INFLUENCES
Default Options
In addition to the standard options, several SD behaviors and policy options can be changed by editing
the default values found in:
HP-UX 11i Version 3: March 2012 − 3 − Hewlett-Packard Company 3