| Message ID | 20260507121644.401811-1-richard.purdie@linuxfoundation.org |
|---|---|
| State | Under Review |
| Headers | show |
| Series | kernel: Disable module deploy tarball by default | expand |
diff --git a/meta/classes-recipe/kernel-artifact-names.bbclass b/meta/classes-recipe/kernel-artifact-names.bbclass index 1a7611a15e8..6d974663321 100644 --- a/meta/classes-recipe/kernel-artifact-names.bbclass +++ b/meta/classes-recipe/kernel-artifact-names.bbclass @@ -31,7 +31,7 @@ KERNEL_FIT_BIN_EXT ?= "${KERNEL_ARTIFACT_BIN_EXT}" MODULE_TARBALL_NAME ?= "${KERNEL_ARTIFACT_NAME}" MODULE_TARBALL_LINK_NAME ?= "${KERNEL_ARTIFACT_LINK_NAME}" -MODULE_TARBALL_DEPLOY ?= "1" +MODULE_TARBALL_DEPLOY ?= "0" INITRAMFS_NAME ?= "initramfs-${KERNEL_ARTIFACT_NAME}" INITRAMFS_LINK_NAME ?= "initramfs-${KERNEL_ARTIFACT_LINK_NAME}"
These module tarballs were once useful for certain development workflows. They are not that useful when deployed in CI, taking up space as release artefacts. Not generating them by default saves time/space and users who need/use them can enable them, this makes more sense as a modern default. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> --- meta/classes-recipe/kernel-artifact-names.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)