Re: [PATCH v7 3/3] meta: Deploy image build artifacts into distro- and image-specific subdirs

["'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>]

On 26.03.26 16:56, Baurzhan Ismagulov wrote:
> 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.
> 

As I wrote: both approaches break our deployment paths. If you want to
release now, do not change anything and discuss which breaking change we
apply afterwards.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
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/fc53e0e9-dbd7-4a50-b5e2-85a35cb5a661%40siemens.com.