From: Benjamin Robin <benjamin.robin@bootlin.com>
To: Marta Rybczynska <rybczynska@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org, ross.burton@arm.com,
peter.marko@siemens.com, jpewhacker@gmail.com,
olivier.benjamin@bootlin.com, antonin.godard@bootlin.com,
mathieu.dubois-briand@bootlin.com, thomas.petazzoni@bootlin.com
Subject: Re: [PATCH v6] sbom-cve-check: Add class for post-build CVE analysis
Date: Fri, 20 Mar 2026 17:14:44 +0100 [thread overview]
Message-ID: <9699867.rMLUfLXkoz@brobin-bootlin> (raw)
In-Reply-To: <CAApg2=QPoTedChybGx6gC8pQek57mfxd0jrtFZwBmJ5YyJ=ZhQ@mail.gmail.com>
Hello Marta,
On Friday, March 20, 2026 at 4:54 PM, Marta Rybczynska wrote:
> > ---
> > meta/classes-recipe/sbom-cve-check.bbclass | 121
> > +++++++++++++++++++++
> > meta/conf/distro/include/maintainers.inc | 2 +
> > meta/conf/fragments/yocto/sbom-cve-check.conf | 14 +++
> > meta/recipes-core/meta/sbom-cve-check-config.inc | 4 +
> > .../meta/sbom-cve-check-update-cvelist-native.bb | 12 ++
> > .../recipes-core/meta/sbom-cve-check-update-db.inc | 28 +++++
> > .../meta/sbom-cve-check-update-nvd-native.bb | 12 ++
> > 7 files changed, 193 insertions(+)
> >
> >
> Hello,
> That looks cleaner than the previous version. How long does the intiial
> build take with
> this fetcher?
>
> Kind regards,
> Marta
I am not sure to understand the question.
With this fetcher, the duration of the initial clone is a "bit" slower,
since we are not doing a shallow clone. If the download directory is
not deleted, the initial fetch is done only once.
The fetch can be realized in parallel with the build of the packages,
and it really depends of your internet connection and of the build
machine.
But if I run:
$ bitbake -c cleanall sbom-cve-check-update-cvelist-native \
sbom-cve-check-update-nvd-native
Followed by:
$ time bitbake sbom-cve-check-update-cvelist-native \
sbom-cve-check-update-nvd-native
The time elapsed is 5m10.211s
I hope this answer your question.
--
Benjamin Robin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-03-20 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 15:42 [PATCH v6] sbom-cve-check: add CVE analysis tool and class Benjamin Robin
2026-03-19 15:42 ` [PATCH v6] sbom-cve-check: Add class for post-build CVE analysis Benjamin Robin
2026-03-20 15:54 ` Marta Rybczynska
2026-03-20 16:14 ` Benjamin Robin [this message]
2026-03-23 8:28 ` Antonin Godard
2026-03-23 10:29 ` Benjamin Robin
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=9699867.rMLUfLXkoz@brobin-bootlin \
--to=benjamin.robin@bootlin.com \
--cc=antonin.godard@bootlin.com \
--cc=jpewhacker@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=olivier.benjamin@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.com \
--cc=rybczynska@gmail.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox