From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Zhihang Wei <wzh@ilbers.de>, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v7 3/3] meta: Deploy image build artifacts into distro- and image-specific subdirs
Date: Thu, 26 Mar 2026 16:56:27 +0100 [thread overview]
Message-ID: <acVXKxkEEhpASHqN@abai.de> (raw)
In-Reply-To: <30fc26f8-c8fc-4647-811e-df76a909ccc7@siemens.com>
On 2026-03-26 07:03, 'Jan Kiszka' via isar-users wrote:
> A tmp split would go beyond dtbs. And I still haven't read concretely
> what makes Isar so different from OE when it comes to deployment.
>
> Irrespective of that, multiconfig is not as prominently used with Isar
> as it is used in Isar itself. The vast majority of downstream
> deployments is single config. The only unavoidable use cases are
> installer-like scenarios (image-in-image). Whenever you can build
> separately, you parallelize, even when duplicating some steps. Only few
> downstreams can wait for builds as long as we do in upstream for the
> testsuite.
Evaluating splitting tmp would delay the release. I'd propose to apply the
updated version, proceed with the release and revisit this topic afterwards.
With kind regards,
Baurzhan
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/acVXKxkEEhpASHqN%40abai.de.
next prev parent reply other threads:[~2026-03-26 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 16:26 Deploy DTBs and other image artifacts into subdirs to avoid conflicts Zhihang Wei
2026-02-26 16:26 ` [PATCH v7 1/3] wic: Obtain real machine name in isoimage source plugin Zhihang Wei
2026-02-26 16:26 ` [PATCH v7 2/3] testsuite: Add testcases to check dtb deployment Zhihang Wei
2026-02-26 16:26 ` [PATCH v7 3/3] meta: Deploy image build artifacts into distro- and image-specific subdirs Zhihang Wei
2026-03-02 9:45 ` 'Jan Kiszka' via isar-users
2026-03-03 10:22 ` Zhihang Wei
2026-03-03 12:50 ` 'Jan Kiszka' via isar-users
2026-03-03 13:35 ` Zhihang Wei
2026-03-24 14:36 ` Zhihang Wei
2026-03-24 14:48 ` 'Jan Kiszka' via isar-users
2026-03-25 16:41 ` Baurzhan Ismagulov
2026-03-26 6:03 ` 'Jan Kiszka' via isar-users
2026-03-26 15:56 ` Baurzhan Ismagulov [this message]
2026-03-27 6:33 ` 'Jan Kiszka' via isar-users
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=acVXKxkEEhpASHqN@abai.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=wzh@ilbers.de \
/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