From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>, daniel.turull@ericsson.com
Cc: openembedded-core@lists.openembedded.org,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
Yocto TSC <tsc@lists.yoctoproject.org>
Subject: Re: [OE-core] [scarthgap][PATCH 1/2] package: export debugsources in PKGDESTWORK as json
Date: Mon, 23 Jun 2025 22:33:26 +0100 [thread overview]
Message-ID: <a041e18e26dc44c399aa86b6c8ecef15eb3dcbaa.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAOSpxdaq52nk4PmHEjnm3P2yc4EPh+A_JEAgewbLHeQJtgMotg@mail.gmail.com>
On Thu, 2025-06-19 at 08:23 -0700, Steve Sakoman wrote:
> Since this is a feature addition the TSC will need to approve it
> before I can take this backport.
>
> I've copied the TSC so they can add this to the agenda for their next
> meeting.
The TSC discussed this today. The change adds a single data file to
packagedata based on existing information we already calculate during
the build so the potential risk and impact on existing users is low.
Whilst this is a feature change, the uses for security and handling
CVEs are extremely useful so on balance the TSC thinks this can be
merged.
Cheers,
Richard
(on behalf of the YP TSC)
next prev parent reply other threads:[~2025-06-23 21:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 8:47 [scarthgap][PATCH 1/2] package: export debugsources in PKGDESTWORK as json daniel.turull
2025-06-19 8:47 ` [scarthgap][PATCH 2/2] spdx: add option to include only compiled sources daniel.turull
2025-06-19 15:23 ` [OE-core] [scarthgap][PATCH 1/2] package: export debugsources in PKGDESTWORK as json Steve Sakoman
2025-06-19 15:30 ` Daniel Turull
2025-06-23 21:33 ` Richard Purdie [this message]
2025-06-24 7:55 ` Daniel Turull
2025-06-25 15:27 ` Steve Sakoman
2025-06-25 15:30 ` Daniel Turull
2025-06-26 11:37 ` Daniel Turull
2025-06-26 20:13 ` Steve Sakoman
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=a041e18e26dc44c399aa86b6c8ecef15eb3dcbaa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=daniel.turull@ericsson.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.com \
--cc=tsc@lists.yoctoproject.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