recipes-core: images: Add tisdk-thinlinux-image
PATCH 1/1 recipes-core: images: Add tisdk-thinlinux-image
Currently we have tisdk-tiny-image tisdk-base-image and tisdk-default-image which serve certain purpose for the users.
However, These are either too heavy or too pointed towards validation.
Hence, let us introduce a basic thinlinux image that has the basic system configured for out of box container usage without changing the meaning of existing image content definitions.
---
NOTE:
https://git.yoctoproject.org/meta-arago/commit/?h=dunfell&id=18b28d0b3a2c1ac3ea6e6149496140a2110e7729
https://git.yoctoproject.org/meta-arago/commit/?h=dunfell&id=55b210e146a5dfcb1a1eca5cad6ea8fab79a5099
https://git.yoctoproject.org/meta-arago/commit/?h=dunfell&id=189de1b80876af739dde88315f5da5b59bc084e1
Now introduces a regression in the sense that 8.1 release that used to support docker out of box (in base,default images) unfortunately do not anymore. Instead users need to mandatorily use a packagefeed to get docker enabled.
This image configuration helps restore that image support.
.../images/tisdk-thinlinux-image.bb | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 meta-arago-distro/recipes-core/images/tisdk-thinlinux-image.bb
meta-arago-distro/recipes-core/images/tisdk-thinlinux-image.bb new file +25 -0
@@ -0,0 +1,25 @@ +# Arago TI Thin Linux image +# Minimal bootable image with container to start the next complex system up. + +require arago-image.inc + +SPLASH = "${@bb.utils.contains('MACHINE_FEATURES','gpu','psplash','',d)}" + +# Allow users to tack on additional packages as interesting. +ARAGO_THIN_IMAGE_EXTRA_INSTALL ?= "" + +IMAGE_INSTALL += "\ + packagegroup-arago-base \ + packagegroup-arago-console \ + packagegroup-arago-base-tisdk \ + ${@bb.utils.contains('MACHINE_FEATURES','gpu','packagegroup-arago-tisdk-graphics','',d)} \ + docker \ + ${ARAGO_THIN_IMAGE_EXTRA_INSTALL} \ +" + +export IMAGE_BASENAME = "tisdk-thin-image" + +# Disable ubi/ubifs as the filesystem requires more space than is +# available on the HW. +IMAGE_FSTYPES_remove_keystone = "ubifs ubi" +IMAGE_FSTYPES_remove_omapl138 = "ubifs ubi"
Signature · 1 line
2.17.1
Review
Quoted 7 lines
(quoted diff) +2
-0+# Allow users to tack on additional packages as interesting. +ARAGO_THIN_IMAGE_EXTRA_INSTALL ?= ""
Is this standard practice? I would have thought that a user would create a bbappend from their layer.
Quoted 10 lines · Jonathan Humphreys via lists.yoctoproject.org
Review
Quoted 7 lines
(quoted diff) +2
-0+# Allow users to tack on additional packages as interesting. +ARAGO_THIN_IMAGE_EXTRA_INSTALL ?= ""Is this standard practice? I would have thought that a user would create a bbappend from their layer.
It's one of the supported ways. E.g. OE-Core has CORE_IMAGE_EXTRA_INSTALL for core images to support this (see section 7.2.1):
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#usingpoky-extend-customimage
Signature · 4 lines
Regards, Denys Dmytriyenko <[email protected]> PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964 Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964