public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [RFC][PATCH] linux-custom: Migrate to a bbclass
Date: Thu, 30 Oct 2025 12:26:35 +0100	[thread overview]
Message-ID: <127cc275-5e09-4044-8154-5cc7ebf74813@siemens.com> (raw)
In-Reply-To: <b4271485-2cfe-4717-a75a-1ba6f982ce47@siemens.com>

On 29.10.25 19:15, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> "inherit linux-kernel" is shorter and a more common pattern compared to
> OE/yocto. Keep the original module.inc as transitional helper, issuing a
> warning when it's used with a migration suggestion.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> Not for application yet, only for getting early feedback if we want such 
> a conversion for all our *-custom.inc cases. Being the one who once 
> started that pattern, I now feel responsible for potentially burying it.
> Yes, will create some noise on user side - unless they are good in 
> ignoring warnings. Builds will continue to work as long as we keep the 
> transitional includes.
> 
>  .../linux-kernel.bbclass}                     |   2 +-
>  meta/recipes-kernel/linux/linux-custom.inc    | 317 +-----------------
>  2 files changed, 7 insertions(+), 312 deletions(-)
>  copy meta/{recipes-kernel/linux/linux-custom.inc => classes/linux-kernel.bbclass} (99%)
> 

I meanwhile realized that we should split our classes/ into
classes-recipe/ (for this kind of classes) and classes-global/ (for
INHERIT'ed ones). Will not be user-visible, thus could be done separately.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
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/127cc275-5e09-4044-8154-5cc7ebf74813%40siemens.com.

      reply	other threads:[~2025-10-30 11:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 18:15 'Jan Kiszka' via isar-users
2025-10-30 11:26 ` 'Jan Kiszka' via isar-users [this message]

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=127cc275-5e09-4044-8154-5cc7ebf74813@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