From: Jan Kiszka <jan.kiszka@siemens.com>
To: Srinuvasan Arjunan <srinuvasanasv@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta/classes/template: add BPN to default TEMPLATE_VARS
Date: Tue, 7 May 2024 11:29:55 +0200 [thread overview]
Message-ID: <c23fd791-bfb7-409a-aec1-e75bf8669b41@siemens.com> (raw)
In-Reply-To: <c8ee6f1d-878a-4dd2-b04e-60fdc96eabdcn@googlegroups.com>
On 07.05.24 07:24, Srinuvasan Arjunan wrote:
>
>
> On Monday, May 6, 2024 at 12:46:47 PM UTC+5:30 srinuv...@siemens.com wrote:
>
> From: Srinuvasan A <srinuv...@siemens.com>
>
> Add the base recipe name (BPN) to default template variables, this
> would be
> helpful to replace the base recipe name in template file if the recipe
> configured BPN across the builds.
>
> Signed-off-by: Srinuvasan A <srinuv...@siemens.com>
> ---
> meta/classes/template.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/template.bbclass
> b/meta/classes/template.bbclass
> index 7f8d5d8f..37e43196 100644
> --- a/meta/classes/template.bbclass
> +++ b/meta/classes/template.bbclass
> @@ -4,7 +4,7 @@
> # SPDX-License-Identifier: MIT
>
> TEMPLATE_FILES ?= ""
> -TEMPLATE_VARS ?= "PN PV DESCRIPTION HOMEPAGE MAINTAINER DISTRO_ARCH"
> +TEMPLATE_VARS ?= "BPN PN PV DESCRIPTION HOMEPAGE MAINTAINER
> DISTRO_ARCH"
>
> do_transform_template[vardeps] = "TEMPLATE_FILES ${TEMPLATE_VARS}"
> python do_transform_template() {
> --
> 2.34.1
>
>
> Hi All,
>
> Any feedback on this changes?
>
Please be more patient, specifically with feature extensions, even if
they are small and kind of obvious as this one.
Thanks,
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-05-07 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 7:17 srinuvasan.a
2024-05-07 5:24 ` Srinuvasan Arjunan
2024-05-07 9:24 ` Uladzimir Bely
2024-05-07 9:29 ` Jan Kiszka [this message]
2024-05-07 14:24 ` Srinuvasan Arjunan
2024-05-10 5:46 ` Uladzimir Bely
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=c23fd791-bfb7-409a-aec1-e75bf8669b41@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=srinuvasanasv@gmail.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