fff-babel: Make implementation runtime switchable #201
No reviewers
Labels
No Label
RFC
RFT
WIP
blocked
bsp
bug
build/scripts/tools
duplicate
feature
fixed
layer3
mantis
more details required
needs changes
node
packages/fff
rejected
security
trivial
upstream
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: freifunk-franken/firmware#201
Loading…
Reference in New Issue
No description provided.
Delete Branch "fbl/firmware:bird2-select"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Some users might want to prefer one babel implementation over another
for various reasons. Having to compile the firmware from scratch can be
quite tedious in that case.
Instead, make the babel implementation switchable at runtime.
Currently, the implementation has to be switched manually in
/lib/functions/fff/babel, which is not upgrade-safe. Also, the previous
implementation is currently not restored after test-mode, so switching
implementations should not be done with test-mode.
Das Problem mit dem test-mode lässt sich vermutlich am einfachsten beheben, wenn man die implementation in einem uci setting speichert. Ebenso das persistieren dieser Einstellung, allerdings bin ich mir nicht sicher, ob ich letzteres haben möchte.
fff-babel: Make implementation runtime switchableto Add bird2 as an alternative babel implementationAdd bird2 as an alternative babel implementationto fff-babel: Make implementation runtime switchableClosed in favor of #121
Pull request closed