full.xml: Add libcamera to the manifest

TEST=repo sync with local manifest

Change-Id: I9f859fd3b4a67c3b1978fd661dda7154a1b871cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/manifest/+/1631078
Commit-Queue: Tomasz Figa <tfiga@chromium.org>
Tested-by: Tomasz Figa <tfiga@chromium.org>
Reviewed-by: Chris McDonald <cjmcdonald@chromium.org>
Reviewed-by: Michael Mortensen <mmortensen@google.com>
1 file changed
tree: 1a3fa3ec64a800d30a7b02bc4a874bb1a3725816
  2. README.md
  3. _remotes.xml
  4. full.xml
IMPORTANT: Changes to this repo must also be made in the private manifest repo https://chrome-internal.googlesource.com/chromeos/manifest-internal. Automated sync between manifest-internal and manifest is not yet set up. And, the changes must also be synced to the infra/config file chromeos_repos.star. Without this, the repo will never be picked up by CQ.

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.


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.


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.


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