In particular, sys-fs/lvm2 includes dmsetup, and systemd will fail to
recognise /dev/mapper/usr if that is built without udev support.
This is not a problem in CI, but a fresh SDK will have board packages
installed without their final USE flags in place due to cyclic
dependencies.
Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
This multi-line comment accidentally only has a # prefix on the first
line, which leads to this warning during the build:
--- Invalid atom in /mnt/host/source/src/third_party/coreos-overlay/profiles/coreos/base/package.mask: mask a specific version in hope that the future update may be smaller,
--- Invalid atom in /mnt/host/source/src/third_party/coreos-overlay/profiles/coreos/base/package.mask: who knows.
Add missing prefixes to lines 2 and 3.
Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
This config enables the syscall tracepoints which are mainly used by
different security and observability tools.
The config was moved to common, so it's removed from the AMD64 only
config.
Signed-off-by: Jon Doron <jond@wiz.io>
Prepare the ebuild to be in an upstreamable state:
- hide python dependencies behind the IUSE flag
- move the semanage.conf additions to a patch
- that way, we can add a user patch that changes compression setting
that was added by Gentoo
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Signed-off-by: Krzesimir Nowak <knowak@microsoft.com>
Prepare the changes for upstreaming:
- Hide python dependencies behind the python USE flag.
- Allow using original sources, without Gentoo modifications with the
vanilla USE flag.
- This also hides app-admin/setools dependency behind this USE
flag. I'm not sure if anything in policycoreutils requires
anything from that package - I assumed that Gentoo-provided rlpkg
maybe does.
- Keep using /var/lib/selinux as a SELinux policy directory. We will
use INSTALL_MASK to skip installation of the directory and will add
a tmpfiles config file to coreos-base/misc-files instead.
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Signed-off-by: Krzesimir Nowak <knowak@microsoft.com>
The legacy workflow was deprecated for some time in distutils-r1
eclass and was recently removed. Now specifying the
DISTUTILS_USE_PEP517 variable is mandatory, but there is no distutils
workflow that would match what legacy was doing. The closest ones are
either "no" or "setuptools". I picked "setuptools", but it results in
all the files put inside the site-packages directory. As a workaround,
move some of the files back where they were supposed to be.
While at it, regenerate the patches and update the python
compatibility variable.
