You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Catalyst 4 has totally changed the way repositories are handled. It only
works when the name of the directory containing the repository matches
the configured name of that repository. We already renamed coreos to
coreos-overlay accordingly, but we actually want entirely different
names and more convenient locations too.
The repositories are now known as gentoo-subset and flatcar-overlay, and
they live under scripts/repos. Using the same name as upstream Gentoo
would have been problematic, and just "flatcar" would have looked
awkward in documentation.
I have removed code referencing /mnt/host/source/config rather than fix
it up, as this is no location is no longer used anywhere.
Signed-off-by: James Le Cuirot <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+8-10
Original file line number
Diff line number
Diff line change
@@ -14,20 +14,18 @@ The SDK can be used to
14
14
# Using the scripts repository
15
15
16
16
The repository is meant to be the entry point for Flatcar builds and development.
17
-
Ebuilds for all packages reside in one of 2 subdirectories - [coreos-overlay](sdk_container/src/third_party/coreos-overlay) and [portage-stable](sdk_container/src/third_party/portage-stable/):
17
+
Ebuilds for all packages reside in one of 2 subdirectories - [flatcar-overlay](repos/flatcar-overlay) and [gentoo-subset](repos/gentoo-subset/):
18
18
```
19
19
scripts
20
-
+--sdk_container
21
-
+---------src
22
-
+--third_party
23
-
+------coreos-overlay
24
-
+------portage-stable
20
+
+--repos
21
+
+--flatcar-overlay
22
+
+--gentoo-subset
25
23
```
26
24
27
-
`portage-stable` is kept in alignment with upstream Gentoo and should not contain any modifications (with only minor, well-justified exceptions).
25
+
`gentoo-subset` is kept in alignment with upstream Gentoo and should not contain any modifications (with only minor, well-justified exceptions).
28
26
Consider it a small sub-set of Gentoo.
29
27
30
-
`coreos-overlay` contains significantly modified or even entirely self-written ebuilds.
28
+
`flatcar-overlay` contains significantly modified or even entirely self-written ebuilds.
31
29
32
30
The `scripts` repository makes ample use of tags to mark releases.
33
31
Sometimes, local and origin tags can diverge (e.g. when re-tagging something locally to test a build).
@@ -52,7 +50,7 @@ While work on a native ARM64 native SDK is ongoing, it's unfortunately not ready
52
50
53
51
The container can be run in one of two ways - "standalone", or integrated with the [scripts](https://github.com/flatcar/scripts) repo:
54
52
* Standalone mode will use no host volumes and will allow you to play with the SDK in a sandboxed throw-away environment. In standalone mode, you interface with Docker directly to use the SDK container.
55
-
* Integrated mode will closely integrate with the scripts repo directory and bind-mount it as well as the portage-stable and coreos-overlay directories into the container. Integrated mode uses wrapper scripts to interact with the SDK container. This is the recommended way for developing patches for Flatcar.
53
+
* Integrated mode will closely integrate with the scripts repo directory and bind-mount it as well as the gentoo-subset and flatcar-overlay directories into the container. Integrated mode uses wrapper scripts to interact with the SDK container. This is the recommended way for developing patches for Flatcar.
56
54
57
55
## Standalone mode
58
56
@@ -82,7 +80,7 @@ To start a container in privileged mode with `/dev` available use:
82
80
83
81
This is the preferred mode of working with the SDK.
84
82
Interaction with the container happens via wrapper scripts from the scripts repository.
85
-
Both the host's scripts repo as well as the ebuild paths (portage-stable and coreos-overlay) are made available in the container, allowing for work on these directly.
83
+
Both the host's scripts repo as well as the ebuild paths (gentoo-subset and flatcar-overlay) are made available in the container, allowing for work on these directly.
86
84
The wrapper scripts will re-use existing containers instead of creating new ones to preserve your work in the container, enabling consistency.
0 commit comments