OpenWrt Forum Archive

Topic: Configure using config diff file

The content of this topic has been archived on 6 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi folks,
For our project we use configuration diff files to configure our OpenWRT build. I couldn't find documentation on this, so I've added something:
http://wiki.openwrt.org/doc/howto/build … _diff_file

Feedback is much appreciated.

Actually, you can copy the config diff to .config instead of appending it, and a `make defconfig' will expand that to a full config. No idea if that makes much of a difference.

Thanks lems. I've tried to incorporate that into the wiki.

If you have more details on using the diffconfig.sh script that would be great to. It could use some usage information, some usage comments in the file or even better a --help command.

On git I see "nbd" is the author, but I couldn't find more info on him/her.
http://git.openwrt.org/?p=openwrt.git;a … 95;hb=HEAD

The current wiki article contents look ok to me. diffconfig.sh just creates a diff compared to global "no-device" defaults.

Appending the recipe/changes may leave unnecessary stuff to your .config. Usually it is better to just replace the old .config totally.

One additional tip: using the plain diffconfig output is principally ok, but it still contains unnecessary stuff, as all packages pulled in due to dependencies are listed.

After some manual investigation work you can manually prune it to contain only the "top" packages and delete the ones pulled in  by dependencies. E.g. luci-app-sqm pulls in the actual sqm-scripts, so only the luci-app-sqm is needed.

My own recipe is included as an example in this thread: https://forum.openwrt.org/viewtopic.php … 03#p276103

(Last edited by hnyman on 29 May 2015, 10:40)

I would still like to leave the append part since that allows applying changes to a config that was already tweaked. It's also hard to guess that this is possible.

The manual investigating into which are the "top" packages seems like something that should be automated.

Interesting topic btw, we can improve our current docker buildroot system with that info.
https://forum.openwrt.org/viewtopic.php … 49#p277949
https://github.com/Doodle3D/openwrt-buildroot-example

The discussion might have continued from here.