The wrapper for `foo-config` style scripts updated `$PATH` so it could
call the real script by name instead of full path. However this means
that calls to shell utilities like `sed` may use the board's version
instead of the build host's. This hasn't been a problem in the past
because the board and host happened to be compatible but this may not
always be true.
In other news, come on people, switch to pkg-config already.
The grub configuration needs some updates to handle dealing with booting
the kernel from the ESP rather than from inside the image. We also want to
be able to avoid dealing with signing the config file, so build it into the
binary. Finally, rather than having to cope with signing grub modules, build
the ones we need to boot into the grub image.
This script uses the EC2 volume import tools instead of attaching and
writing to an EBS volume. This mechanism will be useful for creating
AMIs in isolated EC2 regions and can be run from any host with API
access and the EC2 tools.
TODO: Allow region to be specified and automatically create region-local
S3 buckets as needed. This version hard codes a bucket only usable by
our dev AWS account, not prod. Later on: move to a more compact disk
format like VMDK.
Refreshing eclasses and profiles can potentially introduce surprises but
the only notable change I see are fixing the sse2 flag for OpenSSL and
changing SLOTs for cross compilers.
Until recently Gentoo used stand-alone USE flags like `sse2` to toggle
optional CPU features. This has changed to USE_EXPAND style flags like
`cpu_flags_x86_sse2`. Our OpenSSL ebuild pulled in this change in commit
a9285ef530f88a1373c1459c4e20ca1065b24a91 but at the time the profiles
weren't updated to match, resulting in turning off sse2 for our OpenSSL
build.
Cross compiler ebuilds now always act as if the `multislot` USE flag was
on, allowing minor versions to be installed in parallel. e.g.:
- cross-*/gcc-4.8.3: SLOT changes from `4.8` to `4.8.3`
- cross-*/binutils-2.24-r3: SLOT changes from `0` to `2.24`
The new slot for binutils change may require adding a call to
`binutils-config`, similar to `gcc-config`, the next time we upgrade
binutils but for now nothing needs to change.
Packages updated:
eclass
licenses
profiles
scripts
For some reason package moves are not handled automatically in the board
build roots. Add explicit calls to emaint to update cached binary
packages, installed packages, and the world file.
Update eselect and all packages depending on eselect modules using the
old app-admin/eselect-* names for eselect modules. Upstream has moved
the eselect modules to a new category: app-eselect/*
The only impact this has on production images is upgrading
app-crypt/pinentry from 0.8.2 to 0.9.0.
Packages updated:
app-admin/eselect
app-crypt/pinentry
app-editors/emacs
app-shells/bash-completion
dev-lang/python
dev-lang/ruby
dev-util/ctags
Pull in newer EAPI=5 ebuilds, the upstream python eclass has deprecated
EAPI=4 and reports an error if util-linux-9999 isn't using EAPI=5
The version we ship in CoreOS doesn't change.
Update from vim 7.3.762 to 7.4.273. The 7.4.x ebuilds no longer use the
vim.eclass which has been removed upstream. Updating vim in preparation
for syncing the eclasses with upstream.
Packages updated:
app-editors/vim
app-editors/vim-core
scons has been replaced by a standard autotools build system. Beyond
that a few things are different:
- remove GCC 4.8 workaround, the build system handles this now.
- instead of trying to make executing code in a cross-compiled $SYSROOT
work just avoid running the test suite for board builds. The tests
can still run for the native SDK build.
- `make install` now handles at least part of the install process.
