User guide

Appendix B - License File Format
License File Syntax
FLEXnet Licensing End User Guide 117
PACKAGE Lines
The purpose of the PACKAGE line is to support two different licensing needs:
• To license a product SUITE, or
• To provide a more efficient way of distributing a license file that has a large number of
features, which largely share the same FEATURE line arguments.
A PACKAGE line, by itself, does not license anything—it requires a matching
FEATURE/INCREMENT line to license the whole package. A PACKAGE line is shipped by
your software vendor with a product, independent of any licenses. Later, when you purchase a
license for that package, one or more corresponding FEATURE/INCREMENT lines enable the
PACKAGE line.
Example:
PACKAGE package vendor [pkg_version] COMPONENTS=pkg_list \
[OPTIONS=SUITE] [SUPERSEDE[="p1 p2 ..."] ISSUED=date]
SIGN=pkg_sign
Table B-4 lists the PACKAGE line fields. They must appear in the order listed.
Table B-4: PACKAGE Line Fields
Field Description
package Name of the package. The corresponding
FEATURE/INCREMENT line must have the same name.
vendor Name of the vendor daemon that supports this package.
pkg_version Optional field specifying the package version. If specified,
the enabling FEATURE/INCREMENT line must have the
same version.
COMPONENTS=pkg_list List of package components. The format is:
feature[:version[:num_lic]]
Packages must consist of at least one component. Version
and count are optional, and if left out, their values come
from the corresponding FEATURE/INCREMENT line.
num_lic is only legal if OPTIONS=SUITE is not set—in
this case the resulting number of licenses is
num_lic on
the COMPONENTS line multiplied by the number of
licenses in the FEATURE/INCREMENT line. Examples:
COMPONENTS="comp1 comp2 comp3 comp4"
COMPONENTS="comp1:1.5 comp2 comp3:2.0:4"