[roll] Roll fuchsia [bazel_migration] Migrate component/outgoing

lib/svc is a dependency, so it's migrated as well.

component/outgoing is needed by build-info-service package, which is the
first platform C++ package we are migrating.

Marked both component/outgoing and lib/svc as Fuchsia-only since I'm at
it, so they don't get unnecessarily expanded in host toolchains in GN.

Test: fx build --fuchsia_platform @//sdk/lib/component/outgoing/cpp \
 -- --copt=-ffuchsia-api-level=4293918720

Original-Original-Bug: 490178129
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1637194
Original-Original-Revision: 7d70187a69cb62ce79dbf2871fb5a19d10c50cde
GitOrigin-RevId: 786c676a3aafe0eb94bf5300200c11dd8341e072
Change-Id: Icf7d28ed24b752cbac4f07dc0979265f95f5d000
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1638564
Cr-Commit-Position: refs/heads/main@{#194049}
1 file changed
tree: f65b31f2edd699f83c388362a5299446681532e3
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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.