The file header should show general information about the file name and location, author, and a general purpose.
Example 1.2. Exemplary file header
{ /** * File: modules/CRONConfig.ycp * Package: General YaST Modules * Authors: John The Fish <john@thesmallfish.net> * Flags: Stable * * $Id: $ * * This module offers to read, change and write the current * CRON setup for all system users. */ module "CRONConfig"; ... }
File header format:
Attribute: value
Possible Attributes
are:
Authors
Author
Depends
File
Flags
Internal
Module
Package
Summary
Defines the author(s) of the file.
Example 1.4. Multi-line Authors tag
Authors: Wendy Graceful <grace@example.com> Lars Kralewski <lars@example.com>
What does this file / module depend on.
Relative path where is this file located under the base YaST
/usr/share/YaST2/
path.
Defines the default value for the module stability (read: stability of module API).
Possible values are:
Stable
Unstable
If a module is marked as Internal, it will be omitted while generation the YaST overall documentation. This tag is not mandatory, by default a module is not internal.
Textual description of the package (YaST module) that this file belongs to. This tag is obsolete.
Defines the purpose of this file, such as what does do, how it does that, what it uses for that, etc.
Example 1.10. Multi-line Summary tag
Summary: This is a multiline summary for the exemplary YaST module that does nothing and has no valuable content at all.
Summary tag is something special —. You don't need to define the tag itself, just write a multiline text after at the bottom of the comment after the $Id: $ entry.
Example 1.11. Other Multi-line Summary tag
/** * File: modules/DoNothingAtAll.ycp * * ... * * $Id: $ * * This is a multiline summary for the exemplary YaST module * that does nothing and has no valuable content at all. */