OLD | NEW |
1 This directory contains board and variant overlays. When a board is | 1 This directory contains board and variant overlays. When a board is |
2 configured using "setup_board --board <board>" the following overlays are added | 2 configured using "setup_board --board <board>" the following overlays are added |
3 to the make.conf PORTDIR_OVERLAY if they exist: | 3 to the make.conf PORTDIR_OVERLAY if they exist: |
4 | 4 |
5 src/overlays/overlay-<board> | 5 src/overlays/overlay-<board> |
6 src/private-overlays/overlay-<board>-private | 6 src/private-overlays/overlay-<board>-private |
7 | 7 |
8 When a board is configured using "setup_board --board <board> --variant | 8 When a board is configured using "setup_board --board <board> --variant |
9 <variant>" or "setup_board --board <board>_<variant>" the following overlays | 9 <variant>" or "setup_board --board <board>_<variant>" the following overlays |
10 are added if they exist: | 10 are added if they exist: |
(...skipping 26 matching lines...) Expand all Loading... |
37 repository names (taken from the repo_name files in the overlays). This list | 37 repository names (taken from the repo_name files in the overlays). This list |
38 is used to dissambiguate the selection of ebuilds. When two overlays supply | 38 is used to dissambiguate the selection of ebuilds. When two overlays supply |
39 the same ebuild the overlay who's repo_name is listed later in the masters list | 39 the same ebuild the overlay who's repo_name is listed later in the masters list |
40 will be used. The masters list also effects the way that portage searches for | 40 will be used. The masters list also effects the way that portage searches for |
41 eclasses. By having the repo_name "chromiumos" as the last entry in the | 41 eclasses. By having the repo_name "chromiumos" as the last entry in the |
42 masters list portage will correctly find the chromiumos specific eclasses. | 42 masters list portage will correctly find the chromiumos specific eclasses. |
43 | 43 |
44 | 44 |
45 PRIMARY BOARD OVERLAY | 45 PRIMARY BOARD OVERLAY |
46 --------------------- | 46 --------------------- |
47 The overlay-<name> directory is special in that it must exist and must | 47 Each board must have a primary board overlay containing make.conf and a |
48 contain a make.conf and a toolchain.conf. | 48 toolchain.conf file. |
| 49 |
| 50 If src/overlays/overlay-<board> exists, it is used as as the primary board |
| 51 overlay. If there is no src/overlays/overlay-<board> but there is a |
| 52 src/private-overlays/overlay-<board>-private directory, it is used as the |
| 53 primary board overlay. |
49 | 54 |
50 In order to be useful the primary overlay should also contain ebuilds for | 55 In order to be useful the primary overlay should also contain ebuilds for |
51 chromeos-base/board-devices and chromeos-base/board-devices-private. The | 56 chromeos-base/board-devices. The board-devices ebuild is used to override the |
52 board-devices ebuild is used to override the board-devices ebuild provided by | 57 board-devices ebuild provided by the base chromiumos-overlay. |
53 the base chromiumos-overlay. The board-devices-private should be a "null" | |
54 ebuild that is provided so that a private overlay may override it. | |
55 | 58 |
| 59 If src/overlays/overlay-<board> is the primary board overlay it should |
| 60 also contain a chromeos-base/board-devices-private ebuild. The |
| 61 board-devices-private ebuild should be a "null" ebuild that is provided so that |
| 62 a private overlay may override it. |
OLD | NEW |