There are different types of requirements which can be specified in the package meta data.

• OS version
• other packages
• products
• PTFs
• TR

OS Version

The OS version requirement is set with the custom RPM tag for "OS version" (25004) as a string, f. e. 7.4.

Other Packages

Dependencies to other packages are set in the normal RPM fashion, see RPM tags REQUIRE* (1048, 1049, 1050).

Product

Dependencies to installed products can also be expressed with the require tags. The product option is treated as the version. *BASE is treated as version 0. So you can specify either *BASE or 0.

1PRUBY1 >= *BASE

PTF

Dependencies to PTF levels can also be expressed with the require tags. Just specify the PTF which must be installed (status applied, either temporarily or permanently, or superseeded). To specify a product just prefix the PTF with the product id and separate them with an underscore. If a product id is specified then a release level must also be specified.

5770DG1_SI71714 = 7.4

TR

Dependencies to a TR can also be expressed with the require tags. A requirement for each OS version can be added. The requirement name must be TR with the OS version in braces appended after the TR. Only the TR requirement which corresponds to the OS version of the server will be checked. Every other TR requirement will be ignored.

TR(7.3) >= 3
TR(7.4) >= 1

Flags

Flags are used to express what version is expected to fulfill the requirement. Valid flags are =, <, >, >=, <=.

No Version

When you want to express a dependency and the version of the dependency doesn't matter you can just state the name (f. e. package or product name). As long as any version of the dependency is installed the requirement is met.

Version Range

To express a dependency to a version range you can add multiple requirements for the dependency. F. e.

linkedlist >= 1.0.0
linkedlist < 2.0.0

Epoch

Epoch numbers are not supported by iPKG.