Hurdle 5: Identifying Any /etc/config
Interop
Previously:
function Find-InSource { param( [string] $Pattern, [string] $Repository = ".\luci", [string[]] $Extensions = @( ".lua", ".c", ".js", ".mjs" ), [switch] $Verbose ) # ... } & { # Search for `uci` in the source code $hits = Find-InSource -Pattern '(?<!l)uci' -Verbose $hits | ConvertTo-Json -Depth 5 | Out-File "porting/searches/uci/hits.json" -Encoding UTF8 $hits.Keys | Out-File "porting/searches/uci/hits.txt" -Encoding UTF8 }
Task 1: Reviewing Search Results
Some new searches have been added to porting/~search.ps1
. /etc/config
interop search is saved to porting/searches/config/etc.hits.*
Only noteable hit was:
-
modules/luci-lua-runtime/luasrc/model/uci.lua
- This is a Lua abstraction for UCI
- Already planned to be ported to LuMI
Hurdle 6: Identifying Any luci.config
interop
Task 1: Reviewing Search Results
This search has also been added to porting/~search.ps1
. The results are saved to porting/searches/module.hits.*
A few noteable hits:
-
modules/luci-compat/luasrc/cbi.lua
- This is a part of LuCI's Configuration Bind Interface (CBI)
- Helps map UCI configuration files to HTML forms.
- Already planned to be ported to LuMI
-
modules/luci-lua-runtime/luasrc/cacheloader.lua
- This is a new one.
- It's a small cache enabler for LuCI. It appears to be an artifact of the old LuCI architecture (pre-ucode)
-
modules/luci-lua-runtime/luasrc/config.lua
- Quite literally the "luci.config" module.
- Already planned to be ported to LuMI
-
modules/luci-lua-runtime/luasrc/template.lua
- Modifies
luci.config.template
and readsluci.config.main
to provide a template engine for LuCI.
- Modifies
-
modules/luci-lua-runtime/luasrc/model/uci.lua
- This is a wrapper around the
uci
module that provides a more Lua-like interface. - Already planned to be ported to LuMI
- This is a wrapper around the
-
modules/luci-mod-rpc/luasrc/controller/rpc.lua
- Primarily referenced for getting
uci
session time setting. - Already planned to be ported to LuMI
- Primarily referenced for getting
Today's load will be light, as yesterday's took quite a bit of time to go through. Tomorrow, we will be backstepping as we missed reviewing search results within ucode
files.
Top comments (0)