@@ -843,7 +843,7 @@ ROOTFS_FEATURE += "no-generate-initrd"
INITRD_IMAGE could be set to the full name of an initrd image to be found in
DEPLOY_DIR_IMAGE. Downstream layers had to assume how Isar names its image
-artifacts (presently adding a ${DISTRO}-${IMAGE}.initrd.img suffix to initrd
+artifacts (presently adding a ${DISTRO}-${IMAGE}-initrd.img suffix to initrd
images) and insert the build of their initramfs recipe into the image build
pipeline.
@@ -919,3 +919,11 @@ The following includes were considered internal and are no longer available:
The other original includes still exist and inherit the corresponding new
class. However, they issue a warning to perform the recommended conversion
because these transitional includes will eventually be dropped.
+
+### Align custom initramfs deployment name to standard initramfs
+
+While `INITRAMFS_IMAGE_NAME` ended on `.initrd.img`, standard initramfs where
+deployed as `-initrd.img`. This caused confusion and is now even breaking at
+several points as `INITRD_DEPLOY_FILE` is supposed to be used as canonical
+source of the filename. Therefore, switch `INITRAMFS_IMAGE_NAME` to the
+`-initrd.img` suffix as well.
@@ -1,6 +1,6 @@
# Example of a custom initramfs image recipe. The image will be deployed to
#
-# build/tmp/deploy/images/${MACHINE}/isar-initramfs-${DISTRO}-${MACHINE}.initrd.img
+# build/tmp/deploy/images/${MACHINE}/isar-initramfs-${DISTRO}-${MACHINE}-initrd.img
#
# This software is a part of ISAR.
@@ -1,6 +1,6 @@
# Example of a custom initramfs image recipe. The image will be deployed to
#
-# build/tmp/deploy/images/${MACHINE}/isar-initramfs-${DISTRO}-${MACHINE}.initrd.img
+# build/tmp/deploy/images/${MACHINE}/isar-initramfs-${DISTRO}-${MACHINE}-initrd.img
#
# This software is a part of ISAR.
@@ -21,7 +21,7 @@ IMAGE_INSTALL += "${KERNEL_IMAGE_PKG}"
# Name of the image including distro&machine names
IMAGE_FULLNAME = "${PN}-${DISTRO}-${MACHINE}"
-# Deprecated; this would be set to e.g. "${INITRAMFS_RECIPE}-${DISTRO}-${MACHINE}.initrd.img"
+# Deprecated; this would be set to e.g. "${INITRAMFS_RECIPE}-${DISTRO}-${MACHINE}-initrd.img"
INITRD_IMAGE ?= ""
# IMAGE_INITRD should be used instead (variables consumed by this image class should
@@ -9,7 +9,7 @@ STAMPCLEAN = "${STAMPS_DIR}/${DISTRO}-${DISTRO_ARCH}/${PN}-${MACHINE}/*-*"
INITRAMFS_INSTALL ?= ""
INITRAMFS_PREINSTALL ?= ""
INITRAMFS_ROOTFS ?= "${WORKDIR}/rootfs"
-INITRAMFS_IMAGE_NAME = "${INITRAMFS_FULLNAME}.initrd.img"
+INITRAMFS_IMAGE_NAME = "${INITRAMFS_FULLNAME}-initrd.img"
INITRAMFS_GENERATOR_PKG ??= "initramfs-tools"
INITRD_DEPLOY_FILE = "${INITRAMFS_IMAGE_NAME}"
@@ -332,7 +332,7 @@ class InitRdBaseTest(CIBaseTest):
lines='',
bb_should_fail=False):
mc = f'mc:{machine}-{distro.removeprefix("debian-")}'
- initrd_image = f'{initrd}-{distro}-{machine}.initrd.img'
+ initrd_image = f'{initrd}-{distro}-{machine}-initrd.img'
initrd_path = os.path.join(self.deploy_dir_image(machine), initrd_image)
# cleansstate if the initrd image was already built/deployed to verify
@@ -387,7 +387,7 @@ class InitRdTest(InitRdBaseTest):
machine = 'qemuamd64'
lines = [
- f"INITRD_IMAGE = '{initrd}-{distro}-{machine}.initrd.img'",
+ f"INITRD_IMAGE = '{initrd}-{distro}-{machine}-initrd.img'",
f"do_image[depends] += '{initrd}:do_build'"
]
@@ -413,7 +413,7 @@ class InitRdTest(InitRdBaseTest):
# by specifying an invalid recipe name: bitbake should fail.
lines = [
"IMAGE_INITRD = 'not-a-valid-initrd-recipe'",
- f"INITRD_IMAGE = '{initrd}-debian-bookworm-qemuamd64.initrd.img'"
+ f"INITRD_IMAGE = '{initrd}-debian-bookworm-qemuamd64-initrd.img'"
]
self.build_image_with_dependent_initrd('isar-image-ci', initrd, lines=lines,
bb_should_fail=True)