From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 2/2] u-boot-script: Depend on any kernel package
Date: Fri, 14 Jan 2022 17:40:06 +0100 [thread overview]
Message-ID: <d655ebbb-3f56-b8c9-9ade-e80884518ea3@siemens.com> (raw)
In-Reply-To: <20220114135710.72647-3-amikan@ilbers.de>
On 14.01.22 14:57, Anton Mikanovich wrote:
> Make u-boot-script depend on any installed kernel version to fix
> package build conflict for the machines with different KERNEL_NAME
> but same distro and arch.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> meta/recipes-bsp/u-boot-script/u-boot-script_1.1.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-bsp/u-boot-script/u-boot-script_1.1.bb b/meta/recipes-bsp/u-boot-script/u-boot-script_1.1.bb
> index e07deee..db41b75 100644
> --- a/meta/recipes-bsp/u-boot-script/u-boot-script_1.1.bb
> +++ b/meta/recipes-bsp/u-boot-script/u-boot-script_1.1.bb
> @@ -14,7 +14,7 @@ SRC_URI = " \
> file://u-boot-script \
> file://zz-u-boot-script"
>
> -DEBIAN_DEPENDS = "u-boot-tools, linux-image-${KERNEL_NAME}"
> +DEBIAN_DEPENDS = "u-boot-tools, ${ANY_DISTRO_KERNEL}"
>
Did you also check if we could drop the dependency? If not, I will do
that before we settle of this. Would be simpler if it works.
Jan
> do_install() {
> install -v -d ${D}/usr/sbin
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-01-14 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 13:57 [PATCH v2 0/2] Fix u-boot-script packages conflict Anton Mikanovich
2022-01-14 13:57 ` [PATCH v2 1/2] dpkg: Introduce any kernel variables Anton Mikanovich
2022-01-14 16:40 ` Jan Kiszka
2022-01-14 13:57 ` [PATCH v2 2/2] u-boot-script: Depend on any kernel package Anton Mikanovich
2022-01-14 16:40 ` Jan Kiszka [this message]
2022-01-14 17:23 ` Jan Kiszka
2022-01-15 9:57 ` Anton Mikanovich
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=d655ebbb-3f56-b8c9-9ade-e80884518ea3@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.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