No one is known to be using this script, and it no longer works.
If it turns out to have users, the script will need to be updated
to work with the current config file format before re-adding it.
For the less common case where binpkgs are not used, restructure
this so that it builds binpkgs in /usr/${CHOST} without installing
them, use those binpkgs to initialize /build/${BOARD}.
Since EAPI=7 was supported, portage can no longer use different
ROOT and SYSROOT values. The torcx images were installed into a
temporary root directory after being built using the board's
development files. To continue using this setup, the torcx image's
packages are built as normal binary packages for the board root
without being installed, then the binary packages are installed in
the temporary torcx root.
Since EAPI=7 was supported, portage can no longer use different
ROOT and SYSROOT values. This adjusts the paths so that the first
phase builds cross-toolchains under /usr/${CHOST}, then the native
toolchains are built under /build/${BOARD} (as was being done
previously). Now that the cross-toolchain development files can't
be used when building the native toolchain, the headers and libs
are stupidly copied into the board root to be used used and then
overwritten by the board packages as they are built. Since this is
all done in a chroot, these changes shouldn't affect the SDK host.
The new Docker release schedule has a new release every six months
after 18.09, which has a support period longer than our current LTS
versions. Drop the LTS torcx image and let Docker versions promote
normally again.
the ready command prepares the specified groups for the rollout - it
sets the channel to the new version and updates the update percent to
0%. this allows machines to force update, but updates don't get rolled
out automatically.
the roll command configures the rollout strategy. right now it creates a
linear rollout, going from 0% to 100% in the given number of hours for
each group. it uses the default frame size of 60 seconds (it sets it to
be explicit).
updateservicectl removed the update-percent flag from group update to
force users to use the new api. update percents are now modified using
the group percent command.
This will run on ESXi 6.0 and above, and all non-EOL versions of Fusion
and Workstation.
Also enable a few useful VMX features (HPET; CPU and memory hotplug) that
are added by VMware Workstation 14.1.1's Change Hardware Compatibility
wizard. Correspondingly, enable CPU/memory hotplug in the OVF; omit
HPET because there's no obvious way to enable it.
