openSUSE:Standards YaST2 Repository Metadata patterns

Jump to: navigation, search

Pattern (.pat) files

Attributes of Patterns

  • Name, Version, Release, Architecture
    The architecture restricts the pattern to systems supporting this architecture but no better architecture.
  • Summary, Description
    A short and a long user-readable explanation
  • Group
    A group (or category) this pattern belongs to. Used when displaying patterns in a tree-like widget to the user.
  • Sort oder
    How to order the presentation of multiple pattern within the same group
  • Requires, Provides, Obsoletes, Conflicts, Recommends, Suggests, ...
    Targetting other patterns or packages.


Patterns replace the old Selection format.

Syntax of pattern files

The pattern file starts with a header describing parser requirements, followed by any number of pattern entries.

Header keywords

Keyword Value Comment
=Ver: Syntax version Minimal parser version needed to parse this file.
Should be set to 5.0 for Code10

Pattern entry keywords

Keyword Value Comment
=Pat: name version release architecture This tag starts a new pattern entry. All four values are mandatory
=Sum: summary one line label in default language
=Sum.lang: summary one line language specific label
+Des:
-Des:
description Multi line description in default language
+Des.lang:
-Des.lang:
description Multi line description, language specific
=Cat: category one line user-visible category grouping different patterns (in default language)
=Cat.lang: summary one line language specific category
=Ico: icon icon name
if no icon name is specified, the pattern name will be used instead (with blanks in the name replaced by underscores "_")
".png" will be appended, if there is no ".png" or ".jpg" extension
if no path is specified, icons are looked up in the theme icon path (first /usr/share/YaST2/theme/current/icons/32x32/apps/, then /usr/share/YaST2/theme/current/icons/48x48/apps/)
relative paths are assumed to be relative to the theme path (/usr/share/YaST2/theme/current/)
absolute paths are allowed, too
=Vis: visibility visibility of selection (for user interface)
=Ord: ordering order of selection (for user interface)
This three-digit-integer-value defines the order of the selection when listing multiple patterns in the user interface
+Inc:
-Inc:
pattern dependencies YaST-UI hint: also include these patterns content.
+Ext:
-Ext:
pattern dependencies YaST-UI hint: extends patterns (reverse include).
Dependencies referring to patterns:
+Prv:
-Prv:
pattern dependencies Tags provided by this pattern
+Req:
-Req:
pattern dependencies Required patterns
+Rec:
-Rec:
pattern dependencies Recommended patterns
+Con:
-Con:
pattern dependencies Conflicting patterns
+Obs:
-Obs:
pattern dependencies Obsoleted patterns
+Fre:
-Fre:
pattern dependencies Freshened patterns
+Sup:
-Sup:
pattern dependencies Supplemented patterns
+Sug:
-Sug:
pattern dependencies Suggested patterns (unused?)
+Enh:
-Enh:
pattern dependencies Enhanced patterns (unused?)
Dependencies referring to packages:
+Prq:
-Prq:
packages dependencies list of required (must) packages to install
(see below)
+Prc:
-Prc:
packages dependencies list of recommended (should) packages to install
+Pcn:
-Pcn:
packages dependencies Conflicting packages
+Pob:
-Pob:
packages dependencies Obsoleted packages
+Pfr:
-Pfr:
packages dependencies Freshened packages
+Psp:
-Psp:
packages dependencies Supplemented packages
+Psg:
-Psg:
packages dependencies Suggested packages (unused?)
+Pen:
-Pen:
packages dependencies Enhanced packages (unused?)