Re: [OE-core] [PATCH] rpm-sequoia-crypto-policy: add nativesdk to BBCLASSEXTEND

[Clayton Casciato <majortomtosourcecontrol@gmail.com>]

> On Mon, 29 Sept 2025 at 15:47, Clayton Casciato
> <majortomtosourcecontrol@gmail.com> wrote:
>> I understand the pushback against unnecessary functionality.
>>
>> I would still like to resolve the case where "sequoia" is in the ??. 
>>
>> What are your thoughts on this alternative?
>>
>> PACKAGECONFIG:remove:class-nativesdk = "sequoia"
>@
> I would rather add it separately like the signing selftest does:
>@
> meta/lib/oeqa/selftest/cases/signing.py:        feature +=
> 'PACKAGECONFIG:append:pn-rpm-native = " sequoia"\n'
> meta/lib/oeqa/selftest/cases/signing.py:        feature +=
> 'PACKAGECONFIG:append:pn-rpm = " sequoia"\n'
>@
> _remove works 'after the fact' and complicates understanding how the 
> configuration ends up with the final values. It also cannot be undone
> with any other statement.
>@
> Alex
I will reconsider for the future, but I typically manipulate the 
non-specific PACKAGECONFIG as suggested by the documentation:
https://docs.yoctoproject.org/dev/ref-manual/variables.html#term-PACKAGECONFIG

This was a frustrating issue to encounter as I had not come across this
behavior before for other recipes.

I see the downside to using a remove operation.
With that said, it is discoverable via bitbake-getvar.

While this does seem like a bug, I plan to drop this issue for now.

Thanks again!

Clayton Casciato