[0/1] Add CPE_NAME to os-release

Message ID	20230503111938.942018-1-akuster808@gmail.com
Headers	show Return-Path: <akuster808@gmail.com> ip: 209.85.219.177, mailfrom: akuster808@gmail.com) From: Armin Kuster <akuster808@gmail.com> To: openembedded-core@lists.openembedded.org Subject: [PATCH 0/1] Add CPE_NAME to os-release Date: Wed, 3 May 2023 07:19:37 -0400 Message-Id: <20230503111938.942018-1-akuster808@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit
Series	Add CPE_NAME to os-release \| expand [0/1] Add CPE_NAME to os-release [1/1] os-release: Add CPE_NAME

Message ID

20230503111938.942018-1-akuster808@gmail.com

Headers

From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Add CPE_NAME to os-release
Date: Wed,  3 May 2023 07:19:37 -0400
Message-Id: <20230503111938.942018-1-akuster808@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Series

Add CPE_NAME to os-release | expand

Message

akuster808 May 3, 2023, 11:19 a.m. UTC

I am sending this change as several recipes in meta-security
interogate the system to determine which OS is running so that
they can behave accordingly. I would prefer core carry this
rather than meta-security. This may also help with the overall
OE/Yocto Security story.

Armin Kuster (1):
  os-release: Add CPE_NAME

 meta/recipes-core/os-release/os-release.bb | 8 ++++++++
 1 file changed, 8 insertions(+)