public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "akash hadke" <akash.hadke@kpit.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [poky][master][kirkstone][PATCH] cve-check.bbclass: Add anonymous function to get patched CVEs from recipe
Date: Thu, 21 Jul 2022 03:37:19 -0700	[thread overview]
Message-ID: <27704.1658399839145141718@lists.openembedded.org> (raw)
In-Reply-To: <44426023-FCC1-48A2-BCB4-596DE17AE586@arm.com>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

On Wed, Jul 20, 2022 at 05:11 PM, Ross Burton wrote:

> 
> 
>> On 19 Jul 2022, at 08:54, akash hadke via lists.openembedded.org
>> <akash.hadke=kpit.com@lists.openembedded.org> wrote:
>> 
>> Actually, I wanted to get all patched CVE numbers from a recipe in one
>> variable, and the value of that variable will be used in other tasks. And
>> for this purpose, I used the anonymous function because without it I will
>> not be able to get the value of CVE_PATCHED in other tasks.
> 
> I’ll be blunt: we’re not adding a scan of every file to every recipe in
> every build to this class.
> 
> Why not generate this data on-demand in the task you’re writing to use it?

Hello Ross,

I am trying to add this data in buildhistory. And getting required data in variables will help me like other variables but I don't know another way to set the value.

[-- Attachment #2: Type: text/html, Size: 921 bytes --]

  reply	other threads:[~2022-07-21 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 10:27 [poky][master][kirkstone][PATCH] cve-check.bbclass: Add anonymous function to get patched CVEs from recipe Akash Hadke
2022-07-12 11:00 ` [OE-core] " Ross Burton
2022-07-12 11:21   ` akash hadke
2022-07-18 15:16     ` [OE-core] " Ross Burton
2022-07-19  7:54       ` akash hadke
2022-07-20 11:41         ` [OE-core] " Ross Burton
2022-07-21 10:37           ` akash hadke [this message]
2022-07-19 18:49 ` Marta Rybczynska
2022-07-20  7:47   ` akash hadke

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=27704.1658399839145141718@lists.openembedded.org \
    --to=akash.hadke@kpit.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox