[roll] Roll fuchsia [appmgr] Implement fuchsia.process.Resolver as a v2 component This protocol is now implemented by a v2 component called `process_resolver` in the core realm. `process_resolver` can resolve packages from the base set only or from the entire universe, depending on a build-time GN flag called `auto_update_packages`. `fuchsia.process.Resolver` is now controlled by a security policy that restricts its usage to the 3 consoles (`fx shell`, serial console and terminal.cml) and CTS tests. We are no longer dependent on `appmgr` for fuchsia.process.Resolver. Original-Bug: 105486 Original-Bug: 106062 Original-Fixed: 103486 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/705111 Size-Review: Saman Sami <samans@google.com> Original-Revision: edcca5e2448229a9ff03e59e5b8bab2a3ac3aafa GitOrigin-RevId: 6ac00ab5ffd103a428209756051ca2abf6e0056d Change-Id: I8f69aaddc3141814c11cc14810a2d24688c70008
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.