The version will now be tracked in the manifest so the old
coreos_version.sh needs to source it from there. Also export variables
with a COREOS_ prefix in addition to CHROMEOS_ since the latter name
isn't really correct. This is particularly true for the data published
via lsb_release.
This includes a new gsutil verison which is not yet in upstream portage
along with new ebuilds for a couple of its dependencies that are also
not in portage:
dev-python/google-api-python-client
dev-python/socksipy-branch
Also, dev-python/python-gflags is included here to apply two extra
patches that fix some unit tests and add mark that it conflicts with the
old version of dev-cpp/gflags that we had been using up until now.
Hopefully all this will be merged upstream soon:
https://bugs.gentoo.org/show_bug.cgi?id=468080
Dependencies updated:
dev-python/crcmod
dev-python/httplib2
dev-python/pyopenssl
dev-python/python-gflags
Additionally, dev-cpp/gflags was also updated because it is a
spectacularly old version that conflicts with python-gflags.
Docker seems to be working fine now under systemd. Some recent code
changes have fixed the problems we were running into before.
What has been tested while running docker directly under systemd:
1. docker run
2. docker pull
3. docker images
4. docker rm
These two mirrors are generated specifically from our own overlays so
they should always include everything we need. The default Gentoo mirror
is provided simply as a sane backup.
emirrordist will refuse to handle files that are not included in the
Manifest file. To keep things happy just sweep across the tree adding
them. (A lot of these packages could actually go away, but that is a
different project for another day).
Many updates from upstream have added files without pruning the old.
This leaves the Manifest file incomplete because it only includes the
new files that were copied with it. This causes errors when building a
distfiles mirror because the tool cannot validate those old files.
No need to keep these old ebuilds around so just delete them.
When installing with the default make.conf in full effect
/etc/init.d/functions.sh will be excluded which is the whole point of
the efunctions package in the first place. This should fix that.
Replace ChromiumOS target binhosts with our own. The auto-generated
files have been stubbed out and configs for targets we don't currently
support have been removed. MARCH_TUNE is now defined here.
After this change target binhosts will defined here and
/etc/make.conf.board and overlay-amd64-generic/make.conf are no longer
used. The new setup_board only creates /etc/make.conf.board_setup.
