Technical data

8. Documentation for Developers
8.3.3. Configuration of Packages
The user’s changes to the package’s configuration are made in the file config/<PACKAGE>.txt.
All the OPT’s variables should begin with the name of the OPT, for example:
#-------------------------------------------------------------------
# Optional package: TELNETD
#-------------------------------------------------------------------
OPT_TELNETD='no' # install telnetd: yes or no
TELNETD_PORT='23' # telnet port, see also FIREWALL_DENY_PORT_x
An OPT should be prefixed by a header in the configuration file (see above). This increases
readability, especially as a package indeed can contain multiple OPTs. Variables associated to
the OPT should — again in the interest of readability — not be indented further. Comments
and blank lines are allowed, with comments always starting in column 33. If a variable including
its content has more than 32 characters, the comment should be inserted with a row offset,
starting in column 33. Longer comments are spread over multiple lines, each starting at column
33. All this increases easy review of the configuration file.
All values following the equal sign must be enclosed in quotes
1
not doing so can lead to
problems during system boot.
Activated variables (see below), will be transferred to rc.cfg, everything else will be ignored.
The only exceptions are variables by the name of <PACKAGE>_DO_DEBUG. These are used for
debugging and are transferred as is.
8.3.4. List of Files to Copy
The file opt/<PACKAGE>.txt contains instructions that describe
• which files are owned by the OPT,
• the preconditions for inclusion in the opt.img resp. rootfs.img,
• what User ID (uid), Group ID (gid) and rights will be applied to files,
• which conversions have to be made before inclusion in the archive.
Based on this information mkfli4l will generate the archives needed.
Blank lines and lines beginning with “#” are ignored. In one of the first lines the version of
the package file format should be noted as follows:
<first column> <second column> <third column>
opt_format_version 1 -
The remaining lines have the following syntax:
<first column> <second column> <third column> <columns following>
Variable Value File Options
1
Both single and double quotes are valid. You can hence write FOO=’bar’ as well as FOO="bar". The use of
double quotes should be an exception and you should previously inform about how an *nix shell uses single
and double quotes.
287