Both subcommands take a SIGDIR argument which is assumed to be within
a git repo we can safely sync. devsign creates commits but does not
(currently) push them, leaving that to the user.
We use gpg --enarmor to convert the torcx manifest binary sigs to ascii
armored ones. Unfortunately --enarmor just wraps the binary blob without
realizing its a signature, which breaks torcx. Pipe the output through
sed to fix the header.
The custom sys-firmware/edk2 package has been replaced by Gentoo's
sys-firmware/edk2-ovmf package now that only amd64 is supported.
This partially reverts 1761d9d071 .
We only support amd64-usr at this point, so this removes a required
step when setting up a new SDK. If the default board is specified
normally or through the environment, it will override this value.
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.
