Technical data

8. Documentation for Developers

8.1. Common Rules

In order to include a new package in the OPT database on the ﬂi4l homepage some rules must

be obeyed. Packages that do not comply with these rules may be removed from the database

without warning.

1. No ﬁle copy actions by the user! ﬂi4l provides a sophisticated system to include the ﬂi4l

packages into the installation archives. All ﬁles that should go to the router are located

in opt/.

2. Pack and compress packets properly: packages must be constructed in a way to allow

eﬀortless unpacking into the ﬂi4l directory.

3. Packages must be completely conﬁgurable via the conﬁg ﬁle. Further editing of conﬁg-

uration ﬁles shall not be required by the user. Keep diﬃcult decisions away from the

users and move them to another part at the end of the conﬁguration ﬁle. Note: ONLY

MODIFY IF YOU KNOW WHAT YOU DO.

4. Another hint for conﬁg ﬁles: by its name it has to be seen clearly which OPT it belongs

to. For example OPT_HTTPD contains the variables OPT_HTTPD, HTTPD_USER_N, a.s.o.

5. Please built binaries as small as possible! If you compile them yourself in FBR please

remember to deactive any unneeded feature.

6. Check for Copyrights! If using template ﬁles please keep in mind to change the Copyright

accordingly. This applies also for conﬁg-, check- and Opt text ﬁles. Replace the Copyright

with your own name. A documentation that was only copied of course has to keep the

7. Please use only free formats as archive types. These are:

• ZIP (.zip)

• GZIP (.tgz or .tar.gz)

Please don’t use other formats like RAR, ACE, Blackhole, LHA . . . Windows-Installer

ﬁles (.msi) or self-extracting archives and installers (.exe) should not be used.

8.2. Compiling Programs

The environment needed for compiling programs is available in the separate package “src"’.

There it is also documented how to compile own programs for ﬂi4l.

284