Libzypp/Metadata/YaST/content

From openSUSE

content (as used pre Code11)

The content file contains information about the product. It is used to create an internal product object used in dependency resolution.

See here for a full description of its syntax.

Bug 223406 covers important aspects of the product semantics and defines the following rules starting with openSUSE 10.2 on:

• PRODUCT will also include the distribution, e.g. openSUSE-DVD9
• VERSION will be 10.2-0 (release will be increased if 10.2 gets remastered)
• DISTPRODUCT will not be touched (for suse_register, to be fixed properly in 10.3)
• PROVIDES product:openSUSE = 10.2 will be added to satisfy generic product dependencies (e.g. addon/extra repositories should require "product:openSUSE = 10.2")
• OBSOLETES will be added

Blanks in the product name will be converted to underscores.

Dependencies

A notable change compared to Code 9 is the possibility to specify a complete set of dependencies for a product.

The content may contain the following keys

• REQUIRES, PREREQUIRES, PROVIDES, CONFLICTS, OBSOLETES, RECOMMENDS, SUGGESTS, SUPPLEMENTS, ENHANCES, REGISTERPRODUCT

All of them can now contain a (space separated) list of resolvables optionally followed by version-release constraints.

Examples (requires)

Any package named suse-release: REQUIRES suse-release

A package named suse-release with version 10.0, release 42: REQUIRES suse-release == 10.0-42

A package named sles-release with version 10, release 1 and the pattern sles-base greater or equal to version 10, release 7:
REQUIRES sles-release == 10-1 pattern:sles-base >= 10.7

SHORTLABEL

This is a short label (max 12 characters) used by some bootloaders with restriction on the length of a label.