File: README.md

package info (click to toggle)
chromium 139.0.7258.127-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,068 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (22 lines) | stat: -rw-r--r-- 1,041 bytes parent folder | download | duplicates (6) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
# About //chromeos/ash/components

This directory contains components that are used by ash-chrome only.
For C++ code, think of //chromeos/ash/components like top-level //components.
Specifically, each component should have its own DEPS to be isolated from
other components.

For example, //chromeos/ash/components/account_manager manages the user's GAIA
accounts, but only on behalf of ChromeOS code.
//components/account_manager_core contains cross-platform support for
accounts.

Some subdirectories contain low-level utility code. For example,
//chromeos/ash/components/disks has utilities for mounting and unmounting disk
volumes.

Much of this code used to live in //chromeos/components. The now sunsetted
Lacros project was extracting browser functionality into a separate binary. As
part of this migration, code used only by the ash-chrome binary moved into "ash"
directories. See the
[Chrome OS source directory migration](https://docs.google.com/document/d/1g-98HpzA8XcoGBWUv1gQNr4rbnD5yfvbtYZyPDDbkaE/edit)
design doc for details.