Technical data

8. Documentation for Developers
8.3.8. Support for Different Kernel Version Lines
Different kernel version lines often differ in some details:
• changed drivers are provided, some are deleted, others are added
• module names simply differ
• module dependencies are different
• modules are stored in different locations
These differences are mostly handled automatically by mkfli4l. To describe the avail-
able modules you can, on one hand expand tests dependant on the version (conditional
regular expressions (Page 296)), or, on the other hand mkfli4l allows version dependant
opt/<PACKAGE>.txt-files. These are then named opt/<PACKAGE>_<Kernel-Version>.txt,
where the components of the kernel version are separated from each other by underscores. An
example: the package “base” contains these files in its opt-directory:
• base.txt
• base_3_14.txt
• base_3_17.txt
the first file (base.txt) is always considered. Both other files are only considered if the kernel
version is called “3.14(.*)” resp. “3.17(.*)”. As seen here, some parts of the version may be
omitted in file names, if a group of kernels should be addressed. If KERNEL_VERSION='3.14.26'
is given, the following files (if existing) are considered for the package <PACKAGE>:
• <PACKAGE>.txt
• <PACKAGE>_3.txt
• <PACKAGE>_3_14.txt
• <PACKAGE>_3_14_26.txt
8.3.9. Documentation
Documentation should be placed in the files
• doc/<LANGUAGE>/opt/<PACKAGE>.txt
• doc/<LANGUAGE>/opt/<PACKAGE>.html.
HTML-files may be splitted, meaning one for each OPT contained. Nevertheless a file
<PACKAGE>.html has to be created linking to the other files. Changes should be documented
in:
• changes/<PACKAGE>.txt
314