lbzip2 is surprisingly fast and is particularly useful for dealing with
large archives and filesystem images. In a similar vein pbzip2 has been
used for handling binary packages for a while but lbzip2 seems a bit
better. Since I plan on using the heck out of lbzip2 add it to the build
and system package sets. While mucking around might as well start
swapping pbzip2 for lbzip2 for consistency's sake although it doesn't
seem to matter much for binary packages. For now we can only switch
make.conf for targets, the host make.conf can't change till everyone's
SDK has lbzip2 installed.
Previously only targets were being built with bindist but we should
build the SDK with it as well. This avoids the re-compile of openssl,
openssh, and freetype when creating a new chroot since the SDK tarballs
are already built with the bindist flag. Also turn the bindist flag back
on for freetype in the target profile, we don't need ClearType sub-pixel
rendering on our systems. :)
This places a dev signing key on disk for testing purposes. As noted in
the ebuild a production key will replace this key when building official
images.
Update to latest release. cros_sdk is still using this file instead of
version.txt in the manifest because it needs a tarball that already
exists when building a new version for the first time. At some point
that will work differently but for now we'll have to keep this file.
We were already using the default for CFLAGS, etc. LDFLAGS had
--as-needed but that has gone into the default Gentoo profile so we
ought to move it there as well. Also, ld's -O1 and -O2 are equivalent so
use the profile default -O1.
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
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).
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.
