Technical data
8. Documentation for Developers
If a variable does not depend on any OPT variables, it is considered active. If it is
depending on an OPT variable, it is precisely active if
• its OPT variable is active and
• its OPT variable contains the value “yes”.
In all other cases the variable is inactive.
Hint: Inactive OPT variables will be set back to “no” by mkfli4l if set to “yes” in
the configuration file, an appropriate warning will be generated then (i.e. OPT_Y='yes'
is ignored, because OPT_X='no'). For transitive dependency chains (OPT_Z depends on
OPT_Y which in turn depends on OPT_X) this will only work reliable, if the names of all
OPT-variables start with “OPT_”.
3. VARIABLE_N: If the first column contains a variable with a “%” in its name, it indi-
cates the number of occurrences of the variable (the so-called N-variable). In case of a
multi-dimensional variable, the occurences of the last index are specified. If the variable
depends on a certain OPT, the N-variable must be dependant on the same or no OPT. If
the variable does not depend on any OPT, the N-variable also shouldn’t. If no N-variable
exists, specify “-” to indicate that.
For compatibility with future versions of fli4l the variable specified here must be identical
with the variable in OPT_VARIABLE where the last “%” is replaced by an “N” and everything
following is removed. An array HOST_%_IP4 must have the N-Variable HOST_N assigned and
an array PF_USR_CHAIN_%_RULE_% hence the N-variable PF_USR_CHAIN_%_RULE_N, and this
N-variable itself is an array variable with the corresponding N-variable PF_USR_CHAIN_N.
All other namings of the N variables will be incompatible with future versions of fli4l!
4. VALUE: This column provides the values a variable can hold. For example the following
settings are possible:
Name Meaning
NONE No error checking will be done
YESNO The variable must be “yes” or “no”
NOTEMPTY The variable can’t be empty
NOBLANK The variable can’t contain spaces
NUMERIC The variable must be numeric
IPADDR The variable must be an IP address
DIALMODE The variable must be “on”, “off” or “auto”
I values are prefixed by “WARN_” an illegal content will not raise an error message and
abort the build by mkfli4l, but only display a warning.
The possible checks are defined by regular expressions in check/base.exp. This file may
be extended and now contains some new checking routines, for example: HEX, NUMHEX,
IP_ROUTE, DISK and PARTITION.
The number of expressions may be extended at any time for the future needs of package
developers. Provide feedback!
In addition, regular expressions can also be directly defined in the check-files, even rela-
tions to existing expressions can be made. Instead of YESNO you could, for example also
write
292










