3 Feb
2015
3 Feb
'15
3:37 p.m.
Did you already read this ?
https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-syst…
yes, we took this as a start for the analysis
btw lime-default options are readed in case of
something missing from lime
Questions :
1.is there any "override" mechanism to stop lime-config touching
original config files or params within ?
2. overall view of the design "/usr/bin/lime-config" ( lua script
with no "lua" extension ?)
3. list of keywords used in "/usr/bin/lime-config" and respective
scripts / files
4. there is some "mingle" between lime and lime-defaults - whats the
meaning of "missing" compared to what.
Next halt : Parsing of lime / lime-defauls and the respective list of
keywords with their actions have to be carved out of the source
btw : we have been really surprised by the numbers of interfaces been
generated and digging deep to find out to which extent they are
necessary and to what use
No organised site to store the documentation to ?
regards
3zl(Reinhard)