Originally by jenneron:

Key points are:

1. We have config fragments in devicepkg-dev package. These fragments enable usb networking, file systems, zram, waydroid, etc
   • depends on !4654 (merged)
2. We have kernel_prepare, kernel_build and kernel_package scripts. kernel packages use it
3. Kernel forks maintain defconfig in their repo, and we specify e.g. _pmos_defconfig="sc8180x_defconfig" in APKBUILD. it is applied automatically in kernel_prepare along with our fragments. Kernel maintainers don't have to maintain pmaports config anymore, instead they only add this single line
4. When using kernel directly from kernel.org we store a defconfig in pmaports. It would be integrated in pmbootstrap kconfig edit for convenience, so development process without defconfig in kernel fork won't be different. Alternative: keep full configs and just apply fragments over them, it should be possible too

We want this in all main/community kernel packages. If you disagree then please explain why in a new comment thread, @craftyguy is optimistic that maybe we can find a way to resolve your objections/concerns!

History / context:

• pmbootstrap#1824
• https://wiki.postmarketos.org/wiki/User:Ollieparanoid/kconfig-fragments-2021-10-05