shallow clone. So we cp across .git directory instead.
…of say kioskresetstation. It's not here anymore, everything is now "curated" in the chroot; https://github.com/Webconverger/webc Hence I'm removing this old irrelevant and misleading build includes, since we don't build from scratch anymore
This option was removed in 3.0.0, themese are now only configured through the config directory (but we were using the default anyway).
In a recent commit, the call to lb binary_hdd was accidentally removed. Also, it seems that using ext4 doesn't work in live-build right now (the allocated image size is too small), so we'll switch back to fat16 for now. Note that this does not completely fix disk builds, there seems to be a problem with the bootloader still.
Set live-build mode to progress-linux
The "progress" mode was renamed to "progress-linux" in live-build 3.0~a67. Since we use an existing chroot, with preinstalled packages and a configured sources.list, this didn't actually break regular builds. However, it did break building hdd images, since the default disk label is based on the mode, but lb_binary_hdd can't handle an empty disk label.
This also means that the build cannot happen with live-build older than 3.0~a62.
This tells the install scripts which kernel flavour to use.
There is now code in the initrd that handles this when needed.
Since it's not guaranteed that there's any branch pointing at HEAD after we cloned from chroot, but we need a ref to point at HEAD to allow (efficient) fetching during upgrades, we create a tag.
This allows the upgrade scripts to regenerate the bootloader configuration during an upgrade, instead of having to monkey-patch the existing configs (which is bound to blow up at some point).