From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/2] u-boot-script: Split packages by kernel
Date: Wed, 12 Jan 2022 14:58:10 +0100 [thread overview]
Message-ID: <9c901622-aff0-551d-8e35-33ac83511a87@siemens.com> (raw)
In-Reply-To: <badecbf5-5e11-dfaa-4790-ba99b0084c31@ilbers.de>
On 12.01.22 14:34, Anton Mikanovich wrote:
> 11.01.2022 18:56, Jan Kiszka wrote:
>> On 11.01.22 16:05, Anton Mikanovich wrote:
>>> 11.01.2022 15:03, Jan Kiszka wrote:
>>>> It makes no sense to build the same package with the same content
>>>> multiple times. We likely rather need to make it depend on a generic
>>>> kernel package / create a generic kernel package name.
>>>>
>>>> Jan
>>>
>>> I'm afraid it will not help - moving this dependency into another
>>> package will also move the issue into this new package.
>>>
>>
>> It will. We just have to make u-boot-script depend on a generic kernel
>> so that this package is only installed after some kernel - no matter
>> which one - is already installed on the target image. There is NO
>> dependency on the concrete kernel in this packages, just study it.
>>
>> Jan
>
> Can you please provide any details about how it can be implemented?
> We have linux-image-generic package in Ubuntu, but not in Debian. And we
> can't just create it, because of the same deps conflict issue in Isar.
> I understood u-boot-script depends on any kernel, but we need to declare
> this 'any' somehow.
>
Two directions to resolve that:
1. make it depend on some linux-image-custom (to-be-added "Provides:" of
our kernels) | linux-image-<list of distro kernels>
2. clarify if a kernel actually has to be installed prior to
u-boot-script or if the kernel script hook isn't enough (or can be
made enough)
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2022-01-12 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 9:36 [PATCH 0/2] Fix u-boot-script packages conflict Anton Mikanovich
2022-01-11 9:36 ` [PATCH 1/2] dpkg: Allow parallel build of different package versions Anton Mikanovich
2022-01-11 9:48 ` Henning Schild
2022-01-11 9:36 ` [PATCH 2/2] u-boot-script: Split packages by kernel Anton Mikanovich
2022-01-11 9:50 ` Henning Schild
2022-01-11 12:03 ` Jan Kiszka
2022-01-11 15:05 ` Anton Mikanovich
2022-01-11 15:56 ` Jan Kiszka
2022-01-12 13:34 ` Anton Mikanovich
2022-01-12 13:51 ` Schmidt, Adriaan
2022-01-12 13:59 ` Jan Kiszka
2022-01-12 13:58 ` Jan Kiszka [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=9c901622-aff0-551d-8e35-33ac83511a87@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