docs: document default kconfig fragments defconfig logic

[ci:skip-grep]
[ci:skip-kconfigcheck]
[ci:skip-vercheck]

Signed-off-by: Aster Boese <asterboese@mailbox.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/8978>
This commit is contained in:
Aster Boese 2026-07-08 20:52:43 +02:00 committed by The Friendly Meow (merge) Bot
parent 532709ae51
commit f039294ad6
No known key found for this signature in database

View file

@ -20,10 +20,9 @@ To convert an existing kernel package to use fragments:
### APKBUILD Changes
Add custom `.config` fragment files to `sources=` and define which defconfig to use:
Add custom `.config` fragment files to `sources=`:
```bash
_defconfig="defconfig"
sources="
$pkgname.config
misc.config
@ -32,6 +31,12 @@ sources="
Verify that `pmb:kconfigcheck-*` categories in the `options=` variable are correct, as these determine which `kconfigcheck.toml` sections are included.
If `pmbootstrap kconfig generate` fails, this may be because the default
`defconfig` config fragment may not be the proper config for the kernel.
Consider adding a `_defconfig="<name of custom defconfig>"` above
`sources=` with the name of whatever config the kernel package's source
provides.
### Creating Custom Fragments
If using a generic defconfig, device-specific drivers may not be enabled. Create a fragment explicitly listing required options, for example: