Chromium OS repo manifest (for `repo init`)

Clone this repo:
  1. 6fd3975 drop old gcc checkout by Mike Frysinger · 14 hours ago master
  2. fda1594 Add support for chromeos-next by Guenter Roeck · 28 hours ago
  3. 724e0bb Revert "Changing manifest to point to the cups-2-2-8 branch" by Bernie Thompson · 2 days ago
  4. e787a2f Changing manifest to point to the cups-2-2-8 branch by David Valleau · 3 days ago
  5. 3985c04 Reland "libdrm: Move to master branch" by Kristian H. Kristensen · 11 days 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.