From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
<isar-users@googlegroups.com>, <adriaan.schmidt@siemens.com>,
<ibr@ilbers.de>, <amikan@ilbers.de>
Subject: Re: [PATCH v5 3/5] add option to control deploy of raw wic partitions
Date: Tue, 20 Sep 2022 14:23:40 +0200 [thread overview]
Message-ID: <20220920142340.4795abba@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <786384b1-5207-b130-2c99-7e706958c8ed@siemens.com>
Am Tue, 20 Sep 2022 10:39:24 +0200
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> On 20.09.22 09:55, Henning Schild wrote:
> > Am Mon, 19 Sep 2022 13:20:33 +0200
> > schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:
> >
> >> This patch adds the WIC_DEPLOY_PARTITIONS option to control
> >> if the raw partition files are deployed by wic.
> >>
> >> We also set the default to not deploy to be closer to OE and to
> >> optimize for the average case.
> >> In addition, this significantly reduces the disk size required to
> >> run the CI.
> >>
> >> An API changelog entry is added.
> >
> > I think the deployment of the partitions was an accident and never
> > intended. Cause might be
>
> We might use that in the context of swu (SWUpdate) file generation.
> Related recipes can be found in
> https://gitlab.com/cip-project/cip-core/isar-cip-core/. But I didn't
> check yet if this particular case is related to the SWUpdate, I just
> know that we package individual partitions in that use case.
Yes that use-case is "known" but still the patch was never created to
support that. I will happily assume that swupdate users never used
those partitions from that accident. But i still proposed a changelog
entry saying a word or two.
Henning
> Jan
>
next prev parent reply other threads:[~2022-09-20 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 11:20 [PATCH v5 0/5] use xz and gzip on host (outside chroot) Felix Moessbauer
2022-09-19 11:20 ` [PATCH v5 1/5] do not crossbuild SDK for host-arch eq dist-arch Felix Moessbauer
2022-09-19 11:20 ` [PATCH v5 2/5] run imager in buildchroot-host on cross Felix Moessbauer
2022-09-19 11:20 ` [PATCH v5 3/5] add option to control deploy of raw wic partitions Felix Moessbauer
2022-09-19 12:03 ` Henning Schild
2022-09-19 12:22 ` Moessbauer, Felix
2022-09-20 7:55 ` Henning Schild
2022-09-20 8:39 ` Jan Kiszka
2022-09-20 12:23 ` Henning Schild [this message]
2022-09-20 10:49 ` Henning Schild
2022-09-19 11:20 ` [PATCH v5 4/5] add test for wic partition deploy logic Felix Moessbauer
2022-09-19 11:20 ` [PATCH v5 5/5] add wic.xz image to qemuarm64-bookworm Felix Moessbauer
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=20220920142340.4795abba@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@ilbers.de \
--cc=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