Re: [oe] [meta-oe][scarthgap][PATCH] kernel-hardening-checker: backport recipe

[Michael Opdenacker <michael.opdenacker@rootcommit.com>]

Greetings.

On 8/20/25 10:28, Gyorgy Sarvari via lists.openembedded.org wrote:
>> However, this has already been accepted in master
>> (https://git.openembedded.org/meta-openembedded/commit/?id=5ae3536204ba3764b03647ab75169ee65ca43531)
>> It's true that meta-oe didn't originally have this recipe, but what's
>> the harm in sharing with LTS users that could have the same need as
>> mine? The risk of breaking tests again meta-oe?
> At the end of the day it's of course the branch maintainer's call if he
> accepts the extra recipe and the testing and maintenance tasks that come
> with it, but I don't recall it happening in recent years.
>
> I think it would make precedent - if this recipe is accepted, why
> wouldn't others be accepted? When does a small addition become an
> unacceptably risky or big one? Stability is boring - and that's the
> point. This of course is just the personal opinion of an internet rando
> (me), and not official in any shape or form.
>
>> I'm reading https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS
>> ... I guess such a backport qualifies as a "new feature". But does this
>> really apply to meta-openembedded which is not officially part of the LTS?
>>
>> On the other hand, mixin layers are supposed to be for "potentially
>> invasive changes", which is not the case here.
>> So, where are such (new) backports supposed to be shared?
> Such backports usually live in product specific layers (sometimes in
> other community layers that take up the task of acting like a mixin
> layer) until the project updates to a release that contains that recipe.

Any further objections to adding this backport to the scarthgap branch 
of meta-oe?

I guess there is no risk of breaking anything else in meta-oe/scarthgap, 
but if we don't want to accept exceptions to the rule (even for meta-oe 
which is not strictly part of the LTS), I'll create my own layer for LTS 
users who could be interested. I guess meta-security won't be a suitable 
candidate the upstream recipe is in meta-oe.

Cheers
Michael.

-- 
Michael Opdenacker
Root Commit
Yocto Project and OpenEmbedded Training course - Learn by doing:
https://rootcommit.com/training/yocto/