Unify kernel flavors in one PKGBUILD

[ventureoo]

Based on #941 changes, but with less drastic changes in PKGBUILD structure.

Closes #750
Closes #894

[1Naim]

I considered doing profiles/flavors as well, but thought that would be restrictive if someone wants to build a custom kernel. I see that you added $_flavor but still kept the rest of the build options.

While this does solve the problem of having too many PKGBUILDs, I worry about the number of variables in the PKGBUILD. (although if u think about it, $_features just moves that into a string instead of a variable).

Aside from that, I don't have much problems with this. I'm fine with it if this gets merged instead of #941.

P.S. on moving rt to $_preempt, somehow that didn't come to mind. it seems fitting though. should probably go there regardless of any of these unification series(es?) gets merged.

[sirlucjan]

Good job, thanks.

[ptr1337]

Didnt review yet fully, but the only problem I do see would be if I want not build a specific variant, e.g deckify/hardened whatsoever.

But likely I would just edit the script then.

[ventureoo]

Didnt review yet fully, but the only problem I do see would be if I want not build a specific variant, e.g deckify/hardened whatsoever.

In this case you just need to select cachyos flavor, which is used by default. It doesn't override any build options, so you can customize your build with environment variables as before.

[1Naim]

In this case you just need to select cachyos flavor, which is used by default.

it'll be a little bit of a problem if you want to build some customized handheld kernel with a different cpusched, since it currently overrides it to BORE.

[Copilot]

Pull request overview

This PR consolidates multiple kernel “flavor” packages into a single linux-cachyos/PKGBUILD that is parameterized via a _flavor preset, and removes the now-redundant per-flavor PKGBUILD directories. It also updates local build helper scripts and the GitHub Actions workflow to build the new unified variants.

Changes:

• Unifies previously separate kernel flavor PKGBUILDs (bore/bmq/eevdf/server/deckify/rt-bore) into linux-cachyos/PKGBUILD using a new _flavor preset mechanism and _package_suffix.
• Updates packaging logic to use the appropriate strip tool (llvm-strip vs strip) during module signing and header packaging.
• Refactors docker-based build scripts and tweaks CI build invocation.

Reviewed changes

Copilot reviewed 18 out of 24 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
script.sh	Refactors docker build helper; now builds removed flavors via env-driven presets.
script-znver4.sh	Same as script.sh, but for the znver4 build image.
script-v3-v4.sh	Refactors v3/v4 build orchestration into helper functions for GCC vs LLVM LTO runs.
linux-cachyos/PKGBUILD	Introduces _flavor presets, unified pkgdesc generation, and uses llvm-strip for LLVM builds during packaging.
linux-cachyos-server/PKGBUILD	Removes standalone server flavor PKGBUILD (now handled by _flavor).
linux-cachyos-server/.SRCINFO	Removes standalone server flavor metadata.
linux-cachyos-rt-bore/PKGBUILD	Removes standalone rt-bore flavor PKGBUILD (now handled by _flavor).
linux-cachyos-rt-bore/.SRCINFO	Removes standalone rt-bore flavor metadata.
linux-cachyos-rc/PKGBUILD	Adds maintainer entry.
linux-cachyos-eevdf/PKGBUILD	Removes standalone eevdf flavor PKGBUILD (now handled by _flavor).
linux-cachyos-eevdf/.SRCINFO	Removes standalone eevdf flavor metadata.
linux-cachyos-deckify/PKGBUILD	Removes standalone deckify flavor PKGBUILD (now handled by _flavor).
linux-cachyos-deckify/.SRCINFO	Removes standalone deckify flavor metadata.
linux-cachyos-bore/PKGBUILD	Removes standalone bore flavor PKGBUILD (now handled by _flavor).
linux-cachyos-bore/.SRCINFO	Removes standalone bore flavor metadata.
linux-cachyos-bmq/PKGBUILD	Removes standalone bmq flavor PKGBUILD (now handled by _flavor).
linux-cachyos-bmq/.SRCINFO	Removes standalone bmq flavor metadata.
.github/workflows/build.yml	Changes CI makepkg flags from --skipchecksums to --skipinteg.

Comments suppressed due to low confidence (3)

script.sh:30

• These _flavor values (server/deckify) do not match the presets accepted by linux-cachyos/PKGBUILD (cachyos-server / cachyos-deckify), so the PKGBUILD will fail with "Invalid preset" for these builds.

build_pkg linux-cachyos -e "_flavor=server" -e _package_suffix=lto
build_pkg linux-cachyos -e "_flavor=deckify" -e _package_suffix=lto

script-znver4.sh:30

• These _flavor values (server/deckify) do not match the presets accepted by linux-cachyos/PKGBUILD (cachyos-server / cachyos-deckify), so the PKGBUILD will fail with "Invalid preset" for these builds.

build_pkg linux-cachyos -e "_flavor=server" -e _package_suffix=lto
build_pkg linux-cachyos -e "_flavor=deckify" -e _package_suffix=lto

linux-cachyos/PKGBUILD:516

• This condition checks for _flavor="deckify", but the preset names accepted earlier in the file use "cachyos-deckify". As written, the deckify-specific kernel config toggles will not be enabled when using the preset.

    if [ "$_flavor" = "deckify" ]; then
        echo "Enabling handheld configs"

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ventureoo]

In this case you just need to select cachyos flavor, which is used by default.

it'll be a little bit of a problem if you want to build some customized handheld kernel with a different cpusched, since it currently overrides it to BORE.

That's now possible with c53f62e

[ventureoo]

Rebased

[Copilot]

Pull request overview

Copilot reviewed 18 out of 24 changed files in this pull request and generated 3 comments.

Suppressed comments (7)

script-v3-v4.sh:34

• This call runs in both the none and thin passes, but the later _use_llvm_lto=none always overrides build_env. The second pass therefore rebuilds linux-cachyos-gcc instead of producing the default ThinLTO linux-cachyos package. Let the per-pass LTO value take effect here.

    build_pkg "$image" linux-cachyos "${build_env[@]}" -e "_flavor=cachyos" -e "_use_llvm_lto=none" -e _package_suffix=gcc

script.sh:24

• This replaces the script's previous default ThinLTO linux-cachyos build with linux-cachyos-gcc, and no subsequent call publishes the default package name. Keep the GCC build, but also build the default LTO flavor so repository updates do not drop linux-cachyos.

build_pkg linux-cachyos -e "_flavor=cachyos" -e "_use_llvm_lto=none" -e _package_suffix=gcc

script-znver4.sh:24

• This replaces the script's previous default ThinLTO linux-cachyos build with linux-cachyos-gcc, and no subsequent call publishes the default package name. Keep the GCC build, but also build the default LTO flavor so repository updates do not drop linux-cachyos.

build_pkg linux-cachyos -e "_flavor=cachyos" -e "_use_llvm_lto=none" -e _package_suffix=gcc

linux-cachyos/PKGBUILD:290

• The PKGBUILD now selects LLVM tools for LTO builds, but _package-headers no longer adds clang, llvm, and lld to runtime dependencies. Installed LTO headers therefore lack the toolchain needed to build external modules; linux-cachyos-rc/PKGBUILD:638-640 retains this dependency for the same case. Restore that conditional dependency in _package-headers.

if _is_lto_kernel; then
    makedepends+=(clang llvm lld)
    source+=("${_patchsource}/misc/dkms-clang.patch")
    _strip_bin=llvm-strip

linux-cachyos/PKGBUILD:243

• The package metadata changed here, but linux-cachyos/.SRCINFO was not regenerated: it still contains the old description and the removed linux-cachyos-lto provides/replaces entries. AUR and repository tooling consuming .SRCINFO will therefore expose metadata that disagrees with the PKGBUILD. Regenerate and commit .SRCINFO.

pkgdesc="Linux kernel by CachyOS with patches and improvements ($(_generate_build_desc))"

linux-cachyos/PKGBUILD:13

• These presets inherit the shared ThinLTO/toolchain-suffix defaults, although every removed flavor PKGBUILD (bore, bmq, eevdf, rt-bore, server, and deckify) defaulted to unsuffixed GCC packages. Using a ready-to-use preset directly therefore produces an LLVM kernel under the legacy unsuffixed package name. Default non-cachyos presets to GCC with no suffix while still honoring explicit environment overrides.

### Ready-to-use named options preset
: "${_flavor:="cachyos"}"

linux-cachyos/PKGBUILD:98

• dynamic is listed as a valid preemption mode, but the selection case only accepts full, lazy, and rt; choosing dynamic reaches _die. Remove it from the documented options unless support is implemented.

## Choose between full, lazy, rt or dynamic

[ptr1337]

makes sense

[ventureoo]

The problem is that b2sums is below source array, and it can't be extended. So we either need to move b2sums to the same place as source array, but this will lead to more complicated checksum updating process.

[1Naim]

This has always been a problem and theres really not a good solution for this since u can't automate the checksums for the conditional source files. I say we just ignore this like we always have.

[ventureoo]

Rebased