Fixes compatibility with a new portage patch that filters EROOT from the
ebuild environment. This newer version sets EROOT as needed in each
phase function so it is safe from filtering.
The PORTAGE_USERNAME and PORTAGE_GRPNAME variables are not exported by
default. The SDK uses them to get portage to run builds as the
developer's uid/gid instead of portage:portage. When running outside of
the SDK use the default portage user and group.
Needed for portage 2.2. Sync URIs are included but not very useful yet
because portage only can do `git pull` but not `git clone`. An extra
helper script will be required to do the initial clone it seems.
Binary packages may be useful for re-installing a package with a
different INSTALL_MASK. Can be used to install debug symbols.
Instead of gluing in a special PROD_INSTALL_MASK for all images use
profiles to configure the differences between the base build root,
production images, and developer images. This offers much more
flexibility and is needed for providing a full dev environment in
developer images.
Using parallel_emerge has been disabled by default for all commands
except build_image for quite a while now, build_image kept it just
because it was still a bit faster than normal emerge. Keeping
parallel_emerge complicates future changes to build_image so it needs to
drop it entirely. Since that means nothing uses it by default we might
as well just rip out support for it entirely.
It appears turning off this flag does not actually prevent perl from
trying to build against gdbm. Enable the flag so dependencies are
consistent with perl's actual behavior.
The pkg-config wrapper re-implemented SYSROOT support because it didn't
work correctly in pkg-config before 0.24. That was released years ago so
it is time to update, custom code broke when paths were outside of /usr
so libraries installed to /lib64 broke things.
With this fixed we don't need to generate our own wrappers.
Upstream bug: https://bugs.gentoo.org/show_bug.cgi?id=517530
Gentoo disabled this functionality because coredumpctl didn't exist yet.
It does now and is pretty slick so lets enable this. Dumps are stored in
/var/lib/systemd/coredump by default. Optionally they can be stored in
the journal by modifying /etc/systemd/coredump.conf
Newer ebuilds appear to fix some issues with systemd integration which
may or may not impact our systems but lvm isn't widely used with CoreOS
so no one has noticed. Most importantly though these sorts of errors are
gone:
Configuration file /run/systemd/generator/lvm2-activation.service is
marked world-inaccessible. This has no effect as configuration data
is accessible via APIs without restrictions. Proceeding anyway.
In 215 resolv.conf moved from /run/systemd/network to
/run/systemd/resolv but there isn't anything to fix references to the
old location (namely existing /etc/resolv.conf symlinks after upgrades).
Adding this rule ensures that those links or any other references
continue to work as they did before.
