#1 Building squidge should not make openwrt config default

[Sebastian Bialy]

I decided to add udhcpd support to busybox and tune some other aspects of openwrt package. However every time I'm using mksquidge_usbroot.py, openwrt configuration is overwritten. This is not very useful since mksquidge_usbroot.py task is far beyond simple make invoking.

Consider splitting build process in two stages:

a) prepare patches, download nessessary files, prepare configuation.

b) run build process itself.

user can easly do anything he wants with openwrt between a and b.

And by the way: seems that recreating config files makes whole build process to recompile some files every time. This does not help much.

[bifferos]

One of the design requirements of Squidge is that I do not have to do a lot of
work to catch up with successive OpenWrt releases. Creating a default Edimax
config helped me to achieve that.

Perhaps if you can expand on a) and b) I will understand better what you mean,
of course a patch would be even better :-).

Incidentally, the split you are talking about is kind-of in effect, if you check
the website it shows you how to customise the build process, but presumably
that's not good enough for your needs. The only difference is, you cannot
run mksquidge_usbroot.py, however you can run the package command after the build.