You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think in the light of hybrid c/lua modules and LFS modules we need a versioning and dependency definition for Lua modules including a version definition for the underlying firmware.
We should create Rocks for the Lua Modules and Hybrid Modules. So it is easy to obtain matching Lua sources for your firmware binary, no matter where you got it from. (online build service or self built)
A challenge might be to define the version of the firmware, so that LuaRocks can detect it to pull matching Rocks.
Ideally this would create an ecosystem which can be used to manage modules external to this project.
Workarounds
Get the files form the matching source tree knowing what you do.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I think in the light of hybrid c/lua modules and LFS modules we need a versioning and dependency definition for Lua modules including a version definition for the underlying firmware.
We should create Rocks for the Lua Modules and Hybrid Modules. So it is easy to obtain matching Lua sources for your firmware binary, no matter where you got it from. (online build service or self built)
A challenge might be to define the version of the firmware, so that
LuaRocks
can detect it to pull matching Rocks.Ideally this would create an ecosystem which can be used to manage modules external to this project.
Workarounds
Get the files form the matching source tree knowing what you do.
The text was updated successfully, but these errors were encountered: