All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Gyorgy Sarvari <skandigraun@gmail.com>
Cc: michael.opdenacker@rootcommit.com,
	openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][scarthgap][PATCH] kernel-hardening-checker: backport recipe
Date: Wed, 20 Aug 2025 08:04:11 +0000 (UTC)	[thread overview]
Message-ID: <e37ef122-48fa-4422-890b-22f9ad8e9d33@rootcommit.com> (raw)
In-Reply-To: <1d47e8eb-0753-47e3-9339-b469f2f141f1@gmail.com>

Hi Gyorgy

Thanks for your reply!

On 8/20/25 09:44, Gyorgy Sarvari wrote:
> On 8/19/25 22:39, Michael Opdenacker via lists.openembedded.org wrote:
>> From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>>
>> This recipe is a Scarthgap backport of kernel-hardening-checker_0.6.10.2.bb
>> in the master branch as of August 19, 2025.
>>
>> Tested on qemux86-64 and on beaglebone-yocto
>>
>> Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>> ---
>>   ...ject.toml-fix-up-license-information.patch | 31 ++++++++++++++
>>   ...-relax-setuptool-version-requirement.patch | 29 +++++++++++++
>>   .../kernel-hardening-checker_0.6.10.2.bb      | 41 +++++++++++++++++++
>>   3 files changed, 101 insertions(+)
>>   create mode 100644 meta-oe/recipes-security/kernel-hardening-checker/files/0001-pyproject.toml-fix-up-license-information.patch
>>   create mode 100644 meta-oe/recipes-security/kernel-hardening-checker/files/0002-pyproject.toml-relax-setuptool-version-requirement.patch
>>   create mode 100644 meta-oe/recipes-security/kernel-hardening-checker/kernel-hardening-checker_0.6.10.2.bb
> Note that new recipes are only accepted in master branch, not in stable
> branches.

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?

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?

Thanks
Michael.

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



  reply	other threads:[~2025-08-20  8:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19 20:39 [meta-oe][scarthgap][PATCH] kernel-hardening-checker: backport recipe michael.opdenacker
2025-08-20  7:44 ` [oe] " Gyorgy Sarvari
2025-08-20  8:04   ` Michael Opdenacker [this message]
2025-08-20  8:28     ` Gyorgy Sarvari
2025-09-04 19:26       ` Michael Opdenacker

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=e37ef122-48fa-4422-890b-22f9ad8e9d33@rootcommit.com \
    --to=michael.opdenacker@rootcommit.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=skandigraun@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.