/usr/bin/pkgdiff [-i attribute]... [-o attribute] [-t action_name[,action_name]...]... [-v name=value]... (file1 | -) (file2 | -)
pkgdiff compares two package manifests and reports differences. One of the manifests can be read from stdin by specifying - in place of the file name. pkgdiff sorts each manifest and action into a consistent order before comparison.
Output is in the following form:
This action is in file2 but not in file1.
This action is in file1 but not in file2.
actionname keyvalue [variant values, if any]
This attribute,value is in file1 but not in file2.
This attribute,value is in file2 but not in file1.
Actions with different variants but the same type and key attribute value are treated as separate actions for purposes of comparison. Thus, actions that change attributes are shown in their complete form rather than as attribute changes.
The following options are supported:
Display a usage message.
Ignore attribute if present during comparisons. File hash values can be ignored with –i hash. This option cannot be used with the –o option. This option can be specified multiple times.
Only report differences in attribute. This option cannot be used with the –i option. This option elides any action changes that do not affect attribute on an action.
Only compare the specified actions. Multiple actions can be specified in a comma-separated list. The value of action_name is one of the actions listed in “Actions” in the pkg(5) man page. For example, the following values could be specified for action_name: file, dir, driver, depend, set. This option can be specified multiple times.
Only compute differences for this variant value. For example, only compute differences for arch=sparc. This variant tag is removed for all actions before comparison. Only one value can be specified per variant. This option can be specified multiple times for different variants.
The following exit values are returned:
No differences were found.
Differences were found.
Invalid command line options were specified.
An error occurred.
An unanticipated exception occurred.
See attributes(5) for descriptions of the following attributes: