From: Jan Kiszka <jan.kiszka@siemens.com>
To: Isar users <isar-users@googlegroups.com>,
Henning Schild <henning.schild@siemens.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH] sstate: Make image cache imagetype-specific
Date: Fri, 17 Dec 2021 12:24:36 +0100 [thread overview]
Message-ID: <0325867c-e05a-c879-a13e-92eb7ec3899e@siemens.com> (raw)
In-Reply-To: <20211217105345.GR22100@yssyq.m.ilbers.de>
On 17.12.21 11:53, Baurzhan Ismagulov wrote:
> On Wed, Dec 15, 2021 at 02:33:58PM +0000, Schmidt, Adriaan wrote:
>> Actually, now that IMAGE_FSTYPES supports generating multiple images
>> with different types at once, multiconfig is the wrong way to go in
>> this scenario.
>
> IIUC, Henning was in favor of keeping multiconfig support
> (https://groups.google.com/g/isar-users/c/r91jryQ9v34/m/8OpAiNXCAgAJ), so this
> patch preserves both multiconfig and multiple image types. If we have consensus
> here, I'm fine with either way.
>
I assume that comment was done prior to our refactorings of the image
classes, pulling OE logic for compression support etc., things that will
make multi-format for single run way more natural and desirable.
The problem of multiplying the workdirs for different format types is
that sharing becomes impossible, and that is against the main
multiconfig goal.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-12-17 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 12:57 Anton Mikanovich
2021-12-15 14:33 ` Schmidt, Adriaan
2021-12-16 9:22 ` Anton Mikanovich
2021-12-16 14:56 ` Jan Kiszka
2021-12-17 10:53 ` Baurzhan Ismagulov
2021-12-17 11:24 ` Jan Kiszka [this message]
2021-12-22 14:56 ` Anton Mikanovich
2021-12-22 15:26 ` Schmidt, Adriaan
2021-12-23 10:55 ` 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=0325867c-e05a-c879-a13e-92eb7ec3899e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=henning.schild@siemens.com \
--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