We might want to change it, but more like "openssl-devel" to try version
3 at some later point in time. The FLAVOUR magic can go gradually, see
next commit.
We only support OpenSSL now and the base build is also not fully
hooked up. Perhaps we can improve the situation later on but for
now just remove the spurious bits leading to errors.
Flip the order of root and swap to allow VM image to grow.
Hook this up in extras.conf and also retrofit a serial console
for being able to test and debug in bhyve (build/boot).
Omit the use of a GPT root label in the ZFS case to deal with
devices names in the way that bsdinstall sets it up. It is
not all that important for ZFS anyway.
The setup likely needs further testing and tweaking to make
sure we emulate bsdinstall zfsboot script properly to avoid
future problems.
The solution on mismatch is rarely providing the override so
try to hint at the user using that another configuration might
be needed to match the build environment.
... and set up a chroot environment to run the proper kldxref in the
isolated environment. It turns out that building kldxref manually
in the host builds one for the host likely with the help of /usr/include
and this fails again for the forward build.
It's the facepalm of the week.
According to e0e08e9a5b this was asked about in the forum back
then, but the plugin hasn't gotten much improvement over the years
and to use it you need an Internet connection which you can also
use to install the plugin.
On a restore you can already sync all missing plugins now which is
also helping in this case.
While here fix a lie and add more documentation. We can switch
the include order for local build configuration to allow for more
thorough override capabilities.
Use the oldest available version. We only keep the current version
and the next in these directories by default, otherwise use SETTINGS
or CONFIGDIR overrides directly.
We do not want to install globs as the matching is very fuzzy and
also we no longer do. To make sure prevent use of globs in
install_packages so we can catch this in nightly builds if it
ever happens.
While here, allow to set a VERSION for core builds which ignores
the tag-version-derivation. It is useful for prerelease building.
Last but not least ADDITIONS should no longer look for SUFFIX so
if you want to build an image with SUFFIX=-devel and use a development
plugin overwrite ADDITIONS accordingly, e.g. ADDTIONS=os-dyndns-devel
So now we either set SETTINGS or CONFIGDIR and if the latter is used
SETTINGS variable is populated from the basename of CONFIGDIR to avoid
having to set two overrides at the same time.
Also add a build.conf.local optional build configuration to make
adjustments beyond our own scope feasible.
Always require build.conf since /dev/null does not work anymore
due to omission of embedded language versions.
The top view CONFIGDIR is not the low level CONFIGDIR in the
build scripts, but for lack of refactoring noise and a catchy
naming scheme let's just leave it where it is.