From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 1/2] dpkg: Introduce any kernel variables
Date: Fri, 14 Jan 2022 17:40:39 +0100 [thread overview]
Message-ID: <ae107e7d-0823-6022-49f2-06ff9c19da7e@siemens.com> (raw)
In-Reply-To: <20220114135710.72647-2-amikan@ilbers.de>
On 14.01.22 14:57, Anton Mikanovich wrote:
> To allow packages to depend on any kernel image or header package add
> following variables:
>
> linux-image-generic - any custom Isar compiled kernel image
> linux-headers-generic - any custom Isar compiled headers
> ANY_DISTRO_KERNEL - any upstream kernel + generic one
> ANY_DISTRO_HEADERS - any upstream headers + generic ones
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> meta/classes/dpkg-base.bbclass | 7 +++++++
> meta/recipes-kernel/linux/files/debian/control.tmpl | 2 ++
> 2 files changed, 9 insertions(+)
>
> diff --git a/meta/classes/dpkg-base.bbclass b/meta/classes/dpkg-base.bbclass
> index cb5ce4a..4655f70 100644
> --- a/meta/classes/dpkg-base.bbclass
> +++ b/meta/classes/dpkg-base.bbclass
> @@ -93,6 +93,13 @@ python() {
> d.setVarFlag('do_apt_fetch', 'noexec', '1')
> d.setVarFlag('do_apt_unpack', 'noexec', '1')
> d.setVarFlag('do_cleanall_apt', 'noexec', '1')
> +
> + distro_kernels = d.getVar('DISTRO_KERNELS', True) or ""
> + d.setVar('ANY_DISTRO_KERNEL', 'linux-image-generic')
> + d.setVar('ANY_DISTRO_HEADERS', 'linux-headers-generic')
Provided we need this (see patch 2):
As you wrote yourself (IIRC), "generic" is used by Ubuntu. We should
avoid name clashes. "linux-image-any"?
Jan
> + for kernel in distro_kernels.split():
> + d.appendVar('ANY_DISTRO_KERNEL', ' | linux-image-' + kernel)
> + d.appendVar('ANY_DISTRO_HEADERS', ' | linux-headers-' + kernel)
> }
>
> do_apt_fetch() {
> diff --git a/meta/recipes-kernel/linux/files/debian/control.tmpl b/meta/recipes-kernel/linux/files/debian/control.tmpl
> index dd0b624..8647736 100644
> --- a/meta/recipes-kernel/linux/files/debian/control.tmpl
> +++ b/meta/recipes-kernel/linux/files/debian/control.tmpl
> @@ -8,6 +8,7 @@ Homepage: http://www.kernel.org/
> Package: linux-image-${KERNEL_NAME_PROVIDED}
> Architecture: any
> Depends: ${KERNEL_DEBIAN_DEPENDS}
> +Provides: linux-image-generic
> Description: ${KERNEL_NAME_PROVIDED} Linux kernel, version @KR@
> This package contains the Linux kernel, modules and corresponding other
> files, version: @KR@.
> @@ -15,6 +16,7 @@ Description: ${KERNEL_NAME_PROVIDED} Linux kernel, version @KR@
> Package: linux-headers-${KERNEL_NAME_PROVIDED}
> Architecture: any
> Depends: ${KERNEL_HEADERS_DEBIAN_DEPENDS}, ${perl:Depends}, ${shlib:Depends}
> +Provides: linux-headers-generic
> Description: ${KERNEL_NAME_PROVIDED} Linux kernel headers for @KR@
> This package provides kernel header files for @KR@ on ${DISTRO_ARCH}
> .
--
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 [this message]
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
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=ae107e7d-0823-6022-49f2-06ff9c19da7e@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