Storage plugin would be now part of three lists. I don't see a reason
why we should not move it to base install instead of installing it on
top of base system. It would be better to have it optional and to have
some dependencies but I think that as it is now it is confusing to user
that storage plugin disappears or appears out of kind of nowhere.

This introduces one additional update step to update ubus right after
updater. This separates ubus update to separate run and should ensure
that broken ubus state is limited to only few packages.

This was suggested by user and it makes sense to allow users to
optionally use these Luci apps.

Although on Gitlab primary branch is set to be master on build servers
it seems to be still test. This is probably because of our local git
cache. This forces build of master.

These patches seems to be already present in tree so we can drop them
from this patch.

This is release based on OpenWRT 19.07.

This reorders some options and marks various sections by name.

This also force enables BTRFS.

HaaS requires fair group scheduler so we should enable it. This ensures
that it is enabled so HaaS can build.

Let's see if upstream fixed problems we had. These no longer apply so we
would have to reimplement them anyway.

Thanks to midnightmagic, who pointed out it on IRC channel #turris on Freenode

Karel Koci authored 5 years ago and Josef Schlehofer committed 5 years ago

Parameter -e is now obsolete and by default, we want to build everything.
Removed it from turris-build.conf.example

Because of that we or users don't need to select packages in make
menuconfig which we or they want to build. Now each package will be selected
but not compiled which depends on user choice.

Also, compile_pkgs shouldn't be run under root or with sudo. Do it as
normal user.

Add TIP and remove the section with make menuconfig as it is no longer
necessary

Let's hope that this fixes problems with kernel 4.19 compilation.

This splits off kernel config to separate file (to be consistent with
common and turris1x section).

It also, for real now, sets 4.19 linux kernel for Turris 1.x.

Switch to 4.19 as we have working patchset for that version. We were
using it up to now but upstream seems to fixed configuration and that
resulted in to again using version from this configuration file so let's
switch it here as well.

In Turris OS 3.x opkg was the package containing
/etc/opkg/distfeeds.conf. This file with TOS 4.0+ was moved by upstream
to base-files. This means hat we also have to move postinst for that
file update to base-files from opkg package. This should fix OPKG feeds
being reseted by update.

Upstream prefixed manufacturer name to target config. This is somewhat
nasty of them but we should stay consistent with them. This updates our
configuration to use that target instead.

This should help us to debug system configuration better to see what
exactly was targeted version. This also helps users to see what they are
dealing with. It in some sense informs them if they are upgrading to new
version or if that is just packages change (because of configuration
change) in same release.