Chromium OS repo manifest (for `repo init`)

Clone this repo:
  1. 0f9f999 [manifest] Update GCC repository. by Caroline Tice · 7 days ago master
  2. 5d19cea manifest: Bump depot_tools again. by Don Garrett · 2 weeks ago
  3. 6652660 depot_tools roll by Mike Frysinger · 2 weeks ago
  4. e186e77 Add third_party/sound-open-firmware git repo to manifest by Bernie Thompson · 3 weeks ago
  5. eee69a3 [manifest] Update GCC commit to get latest retpoline fixes. by Caroline Tice · 3 weeks ago
IMPORTANT: Changes to this repo must also be made in the private manfest repo https://chrome-internal.googlesource.com/chromeos/manifest-internal. Automated sync between manifest-internal and manifest is not yet set up.

Repo Groups

Repo is the tool that we use to manage our local checkouts. It parses the manifest specified by the default.xml file. The name of the manifest can be ovverriden using -m. One could also check out a subset of the manifest using the repo groups feature. This section documents the important groups that are part of the default chromiumos manifest.

minilayout

This group is the minimum subset of repos needed to do a full build of Chrome OS. It doesn't include all of the repos to necessarily test the OS image but does include all those needed to create an iamge.

buildtools

The subset of repos needed to perform release actions i.e. payload generation, etc. Used by release engineers, TPMs, and Infra team members. Note this group isn't useful without a checkout of manifest-internal.

labtools

Tools needed to perform routine lab administrative actions like DUT re-allocation or lab server management.