| commit | 4c26e8d357fbbb595208e9ff3a9d41da981528a9 | [log] [tgz] |
|---|---|---|
| author | Gary Bressler <geb@fuchsia.infra.roller.google.com> | Mon Sep 25 23:54:12 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Sep 25 16:56:01 2023 -0700 |
| tree | 6ba123ef3fe869cfba5721d102efc10bbcc7a5a2 | |
| parent | b98d985bdb1e5b8b08d2f28a5869ec7da41275db [diff] |
[roll] Roll fuchsia [cmc] Improve dep tracking for capability sources Some capability types (`storage`, and soon `dictionary`) themselves have a source in `from`. For example, storage depends on a backing dir, and dictionaries can depend on another dictionary which they're initialized from. The dependency tracking strategy for this today involves replacing the dependency on the capability with a dependency on its source. This may lead to spurious cycles. Instead of replacing the capability with its source dependency, represent the capability as a node in the dependency graph, and add an edge between it and the source. As a bonus, this should make the error more useful. Original-Bug: b/300500098 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/921041 Original-Revision: 13b2aa72e0cfef263e5e59f8717a6961980cb342 GitOrigin-RevId: aa16bdf704639cfde313f385af37d81783cd8abe Change-Id: Iaa26eeaf0dc5999d3eefdd1bf5c0cfb944077472
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.