Hello,

Both variables are defined with "?=", which means that they are allowed to be 
overridden.
And as usual, if something is allowed, someone is also doing that.
That's also why 
https://code.siemens.com/mirror/openembedded-core/-/commit/2a80840a4fe0d38254ed3e9f96c893f6e04db8d8
 was submitted - the empty link name use-case was broken.
That obviously broke the thing that you're trying to fix but your commit is a 
clear revert, so we would be bouncing between error with empty link name and 
error with default link name.
Commit (which is actually not from me) I posted in my previous reply handles 
both cases.

Peter

> -----Original Message-----
> From: [email protected] <openembedded-
> [email protected]> On Behalf Of Anna-Lena Marx via
> lists.openembedded.org
> Sent: Wednesday, July 1, 2026 2:44 PM
> To: [email protected]
> Subject: Re: [OE-core] [PATCH] classes-recipe/sbom-cve-check: fix sstate cache
> mismatch in sbom path
> 
> Hi Peter,
> 
> I'm a bit confused about your patch, not that I would not believe it solves 
> the issue,
> but IMAGE_LINK_NAME is defined as
> 
> `IMAGE_LINK_NAME ?= "${IMAGE_BASENAME}${IMAGE_MACHINE_SUFFIX}"`
> 
> and IMAGE_NAME as
> 
> `IMAGE_NAME ?= "${IMAGE_LINK_NAME}${IMAGE_VERSION_SUFFIX}"`
> 
> means, if I'm not completely confused, if IMAGE_LINK_NAME would be empty for
> some reason, IMAGE_NAME, would only consist of the
> IMAGE_VERSION_SUFFIX.
> This does not read correct to me as well, and thus I'm not completely 
> enthusiastic
> about your version.
> 
> But I'm completely with you in terms of the main issue and would rather like 
> to fix it
> on this level than patching symptoms.
> 
> 
> Anna
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#239983): 
https://lists.openembedded.org/g/openembedded-core/message/239983
Mute This Topic: https://lists.openembedded.org/mt/120061528/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to