[roll] Roll fuchsia [appmgr] Don't start using startup component

Just make appmgr an eager child of core where present.
Also do the same for session-manager while I'm at it.

TODO(later): delete startup.cml entirely.
To unblock this we probably need to pull all the eager children of
core.cml out to shards, and only include them when the packages of the
children are included.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/714864
Original-Revision: e745a5c9b1681cc468eea674d6affcffb885a602
GitOrigin-RevId: b294137ee22bbac372fe7643ec9c7b264bf16df8
Change-Id: I66d4ab4dec8face11e05bb5e2fcc47ae3eebd582
1 file changed
tree: 4d51e2488b916eb28e4b6adc71c1b334b5859f84
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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 via the IRC channel #fuchsia on Freenode.

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.