mkosi: Move all mkosi configuration into mkosi/ subdirectory

Now that mkosi can automatically pick up its main configuration from
a mkosi/ subdirectory if it exists and there is no configuration in the
top level directory, let's make use of it  to reduce the amount of clutter
in the top level directory of the repository.

This will also make it easier to install the mkosi configuration files as
part of the testing packages later on.
This commit is contained in:
Daan De Meyer
2025-04-02 14:27:45 +02:00
parent 478fadde77
commit 342d21ef19
145 changed files with 48 additions and 50 deletions

View File

@@ -86,7 +86,7 @@ not required to write basic patches.
By default, `mkosi` will first build a tools tree and use it build the image and
provide the environment for `mkosi sandbox`. To disable the tools tree and use
binaries from your host instead, write the following to `mkosi.local.conf`:
binaries from your host instead, write the following to `mkosi/mkosi.local.conf`:
```conf
[Build]
@@ -317,6 +317,6 @@ VScode, you'd have to add the following to the VSCode workspace settings of the
```json
{
"clangd.path": "<path-to-systemd-repository>/mkosi.clangd",
"clangd.path": "<path-to-systemd-repository>/mkosi/mkosi.clangd",
}
```

View File

@@ -15,7 +15,7 @@ compiler you want to use and which part of the test suite you want to run.
## mkosi
To build with sanitizers in mkosi, create a file `mkosi.local.conf` and add the following contents:
To build with sanitizers in mkosi, create a file `mkosi/mkosi.local.conf` and add the following contents:
```
[Content]