Hi, On Mon, Nov 4, 2019 at 4:36 PM Adrian Schmutzler <m...@adrianschmutzler.de> wrote: > However, I'm not aware of a case where board.json is used for anything else > than setting up config files, like in a script with user-interaction etc.
While I agree that those are the most common use-cases for board.json, board.json is used by for example luci to determine which parts of network configuration to display. > So, if I want to bring the label MAC address to users updating to > 20.xx/master, I'd either have to use board.json in get_mac_label, or add > label_macaddr for those not having it even though /etc/config/system already > exists. One could still think about providing a label_macaddr option in uci > only for _overwriting_ the provided value. I am not overly familiar with them, but I think this problem can be resolved by a uci-defaults script. As far as I have understood, those scripts are run once and then remove. You could create a script that checks board.json/device tree (basically a combination of the changes in your patch) and update system-config accordingly. BR, Kristian _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
