[roll] Roll fuchsia [fuchsia-component] Split into multiple crates

Split the client, server, and directory modules into separate crates.

The vfs was made into a dylib which saved storage space but regressed
fxfs performance. Ideally, fxfs would depend only on the vfs statically.
Fxfs depends on fuchsia_component both directly and indirectly but only
the client module is used. fuchsia_component depends on the vfs's dylib
but only for the server module. By splitting the client and server
modules into separate crates, fxfs can be made to only depend on the vfs
statically.

Original-Bug: 396172331
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1235844
Original-Revision: 638ac85ce15099a7fcc8163bf84c451bde507042
GitOrigin-RevId: a621ac598f891c710b62a98cdc5525e32c28c274
Change-Id: I012f1cf479e6970cfb6e943b2360d3e67820421f
1 file changed
tree: 56edd180eed9e6b5d9119f32a020e54b21b16332
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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 in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.