We were installing selinux configuration files in /etc which caused problems
on upgrades. Move them into /usr and ensure that systemd sets up appropriate
temporary files. Fixes https://github.com/coreos/bugs/issues/447
Change --no-rebuild to -no-rebuild and drop --banner in the test phase
to match the documentation of go dist.
Gentoo-Commit: fb870ae6f45993ea375d8d5381edb72ade271b06
There are a few quirks with Go to deal with when cross-compiling:
- Since DEPEND cannot distinguish cross-architecture dependencies the
current ebuild cannot keyword all architectures it supports. This
could be resolved in the future with a special use flag or other
clever trick to drop go-bootstrap from DEPEND for cross builds.
- GOHOST* and CC variables are CBUILD values.
- GO* and *_FOR_TARGET variables are CHOST values.
- Go can always be used as a cross-compiler so handling the
CHOST!=CTARGET case isn't strictly required. We could provide a
pre-built copy of the std library for CTARGET's architecture but I'm
not sure if that would be useful or not. For now the ebuild just
doesn't allow that case.
Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558216
Gentoo-Commit: 0f4f3b8d200e15982e5e75f52f3c472d152cc4c9
Run-time binaries must be provided by the SDK, dynamic libraries or the
entire architecture may be different under the target $ROOT.
I have no idea if selinux can be built cross-architecture though, if not
this may need to be revisited with qemu.
- Exclude all python scripts when the python flag is off.
- Add nls use flag to disable gettext
- Add extra use flag to disable Gentoo provided tools and OpenRC goo.
- Drop live ebuild, we don't really need it.
o Enable more ARM64 board support:
EXYNOS7
QCOM
SEATTLE
TEGRA
SPRD
ZYNQMP
o Enable USB wireless and the RTL8192CE driver (with firmware).
Signed-off-by: Geoff Levand <geoff@infradead.org>
The linux-info eclass sets variables referring to the kernel source and
build trees when a binary package is built. This is problematic when
linux-info uses the default build path /lib/modules/$V/build which
includes the built kernel version. So if the kernel has changed since
the docker package was built installing docker from the binary package
will fail, breaking build_image and more. To work around the issue just
make the config checks non-fatal. They really aren't all that useful to
us anyway.
