No subject

Sending patches or new functionality to luci mailing list is also not a choice 
because there is no guarantee that the code is implemented short term.

My idea is to move code of LuCI applications like tinyproxy, samba, hd-idle, ddns-scripts, .....
to OpenWrt/packages as samba/samba-luci, tinyproxy/tinyproxy-luci or ddns-scripts/ddns-scripts-luci.
The mwan3 package already doing this. 

I think this is the best way, because openwrt/packages are moving fast forward 
and needed changes to the corresponding LuCI apps needs to be in sync.

My port/move for luci-app-ddns is ready for take off.

What do you think ?

Christian
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel