From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH v3 27/27] RECIPES-API-CHANGELOG: Document include to class conversion
Date: Sun, 30 Nov 2025 10:27:47 +0100 [thread overview]
Message-ID: <0941592cb33f735f466ea0e746be6295f78e8c2a.1764494867.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1764494867.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
RECIPE-API-CHANGELOG.md | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index c55bcd56..6d7c56b9 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -892,3 +892,30 @@ PREFERRED_PROVIDER_bootstrap-{host,target} in local.conf.
There is no longer the need to explicitly inherit dpkg in custom barebox
recipes if the helper include is used.
+
+### Conversion of recipe helper includes to classes
+
+All recipes helper include like `recipes-kernel/linux/linux-custom.inc` have
+been migrated to classes. The following transitions were applied:
+
+ - `recipes-kernel/linux/linux-custom.inc` -> `linux-kernel.bbclass`
+ - `recipes-kernel/linux-module/module.inc` -> `linux-module.bbclass`
+ - `recipes-kernel/kselftest/kselftest.inc` -> `kselftest.bbclass`
+ - `recipes-bsp/u-boot/u-boot-custom.inc` -> `u-boot.bbclass`
+ - `recipes-bsp/optee-os/optee-os-custom.inc` -> `optee-os.bbclass`
+ - `recipes-bsp/optee-os/optee-os-tadevkit-custom.inc` -> `optee-os-tadevkit.bbclass`
+ - `recipes-bsp/optee-client/optee-client-custom.inc` -> `optee-client.bbclass`
+ - `recipes-bsp/trusted-firmware-a/trusted-firmware-a-custom.inc` -> `trusted-firmware-a.bbclass`
+ - `recipes-bsp/barebox/barebox.inc` -> `barebox.bbclass`
+ - `recipes-initramfs/initramfs-hook/hook.inc` -> `initramfs-hook.bbclass`
+ - `recipes-support/container-loader/docker-loader.inc` -> `docker-loader.bbclass`
+ - `recipes-support/container-loader/podman-loader.inc` -> `podman-loader.bbclass`
+
+The following includes were considered internal and are no longer available:
+
+ - `recipes-bsp/optee-os/optee-os.inc`
+ - `recipes-support/container-loader/container-loader.inc`
+
+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.
--
2.51.0
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/0941592cb33f735f466ea0e746be6295f78e8c2a.1764494867.git.jan.kiszka%40siemens.com.
next prev parent reply other threads:[~2025-11-30 9:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-30 9:27 [PATCH v3 00/27] Use more classes! 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 01/27] linux-custom: Drop redundant template inheritance 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 02/27] meta: Move INHERIT'ed classes into classes-global 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 03/27] meta: Move recipe-pulled classes into classes-recipe 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 04/27] meta-isar: " 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 05/27] linux-custom: Migrate to a bbclass 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 06/27] meta-isar: Switch to linux-kernel class 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 07/27] linux-module: Migrate to a bbclasss 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 08/27] meta-isar: Switch to linux-module class 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 09/27] kselftest: Migrate to a bbclass 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 10/27] meta-isar: Switch to kselftest class 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 11/27] u-boot-custom: Migrate to a bbclass 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 12/27] meta-isar: Switch to u-boot class 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 13/27] optee-os[-tadevkit]-custom: Migrate to bbclass'es 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 14/27] meta-isar: Switch to optee-os[-tadevkit] classes 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 15/27] optee-client: Migrate to a bbclass 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 16/27] meta-isar: Switch to optee-client class 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 17/27] trusted-firmware-a: Migrate to a bbclass 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 18/27] meta-isar: Switch to trusted-firmware-a class 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 19/27] barebox: Add SPDX license identifiers 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 20/27] barebox: Move inherit dpkg into common .inc 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 21/27] barebox: Migrate to a bbclass 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 22/27] meta-isar: Switch to barebox class 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 23/27] initramfs-hook: Migrate to a bbclass 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 24/27] meta[-isar]: Switch to initramfs-hook class 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 25/27] container-loader: Migrate to bbclass'es 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` [PATCH v3 26/27] meta-isar: Switch to {docker,podman}-loader classes 'Jan Kiszka' via isar-users
2025-11-30 9:27 ` 'Jan Kiszka' via isar-users [this message]
2025-11-30 9:29 ` [PATCH v3 00/27] Use more classes! 'Jan Kiszka' via isar-users
2025-12-03 15:09 ` Zhihang Wei
2025-12-03 15:29 ` 'Kiszka, Jan' via isar-users
2025-12-03 15:32 ` Zhihang Wei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0941592cb33f735f466ea0e746be6295f78e8c2a.1764494867.git.jan.kiszka@siemens.com \
--to=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox