commit | d2e19d887deee1f748b1b06918903e9f3a306818 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Thu Feb 27 00:35:50 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Feb 27 18:45:10 2020 |
tree | 947115158e9fccd201e0cab00b823878e01b792f | |
parent | 28f04a1d275460a1a91d979aecefd53c33b1b461 [diff] |
sommelier: add default .sommelierrc to /etc/skel Add a default sommelier user configuration file so it's at least semi-documented. In addition, populate the default .sommelierrc with an example of how to load .Xresources on startup (commented out so default behavior is unchanged). BUG=chromium:927304 TEST=kokoro TEST=bazel build as per README.md Change-Id: Ie030f9e1fc6217c7dbde69a0545e69d5de13a139 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2076591 Reviewed-by: Nic Hollingum <hollingum@google.com> Reviewed-by: David Munro <davidmunro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Daniel Verkamp <dverkamp@chromium.org>
These are the guest packages for setting up a container to integrate with Chrome OS. This includes build scripts that are run in Google's internal continuous integration service.
The guest packages can be built with Bazel.
bazel build //cros-debs:debs --host_force_python=py2
promote\_apt.sh MILESTONE
and promote\_container.sh MILESTONE
in scripts are used to promote containers from staging to live. NOTE: Whatever is the latest in staging is what gets promoted to live so make sure it's what was tested.