Chrome Release Bot (LUCI) 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
..
cellular_setup 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
chromebox_for_meetings 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
device_sync 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
ime 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
multidevice_setup 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
nearby 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
quick_pair 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
recording 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
secure_channel 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
BUILD.gn 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
DEPS 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago
README.md 4762b62e7d Publish DEPS for 106.0.5249.13 1 year ago

README.md

DEPRECATED. If you’re about adding new service for ash-chrome only, consider using //chromeos/ash/components.

This directory holds services that are:

  • Chrome OS UI (ash) specific.
  • They run in their own utility processes, and cannot call ash code directly.
  • Chrome can add a DEP on these services just for the sole purpose of launching them (until ash supports launching its own services).