The new --developer_data option can be used to specify a path to a cloud
config to bundle into the image. If none is provided but a shared user
password (for core) is set then generate a config to set that password.
This lets us use the same mechanism for setting the default password for
both disk and PXE images.
Setting the 'core' user's password is now always handled by cloud
config. As an added benefit this will let us use baselayout as a binary
package now that it doesn't depend on random state it the local SDK.
Autotools is provided by the SDK chroot, not the board sysroot.
Presumably at some point in the ChromeOS past some macros were being
installed the other way around in the sysroot but not the SDK chroot.
Currently this is not the case, so this extra variable can go away.
This image type is the same as the developer image except that it is a
single root filesystem and is bootable via systemd-nspawn. This may
become obsolete eventually when it becomes possible to boot the normal
disk images under nspawn but it is useful for testing until then.
The partition type is defined by the Discoverable Partitions Spec.
http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/
To make it possible to plop a CoreOS install into a simple
single-filesystem image for use as a container some things like
configuring bootloaders need to be skipped.
Slowly moving make.conf into profiles, here is another piece. We never
actually use the built debug information so remove -g to produce a
little less of it. Add -mtune=generic to let GCC optimize for whatever
it thinks the most common processors are.
Upstream has merged all of our reload bug fixes, replace local patches
with the upstream versions.
Drop the patch that removed the check for /etc/os-release. We always
initialize missing files in the initrd so it isn't needed any more.
Dracut is now in portage-stable and DRACUT_MODULES is unused.
Update bootengine dependencies so we can use btrfs and mdadm in the
initrd. Drop kbd because I'm excluding out the terminfo module now.
To behave more like setup_board/build_packages update_chroot should
fully configure portage to make sure everything is accurate.
Now binhosts are defined in make.conf.host_setup so the static config in
coreos-overlays doesn't need to refer to version.txt. setup_board
already made this change in 7a43a07f.
Define path locations to reduce dependency between static configs in
coreos-overlays and the behavior of the scripts repo. Spreading
configuration across two repos makes everything harder to understand.
Eventually everything should either be defined in profiles in
coreos-overlays or minimal auto-generated config files here in scripts.
For the most part this doesn't influence anything. The one exception is
the custom configuration for using curl is dropped, just rely on the
portage defaults. It appears curl was only used to work around a wget
issue with Google's internal SSL certificates. We care not. :)
