From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <paul.eggleton@linux.microsoft.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFC PATCH 1/2] classes/buildhistory: record SRC_URI
Date: Mon, 26 Oct 2020 06:43:01 +0000 [thread overview]
Message-ID: <20201026064259.GT2040@korppu> (raw)
In-Reply-To: <e83e7133cc7affdc013455744f1bc31d83503757.1603080016.git.paul.eggleton@linux.microsoft.com>
On Sun, Oct 18, 2020 at 09:03:56PM -0700, Paul Eggleton wrote:
> From: Paul Eggleton <paul.eggleton@microsoft.com>
>
> It can be useful to record SRC_URI into buildhistory for the purposes of
> tracking exactly which sources got built (we already have SRCREV) as
> well as getting an indication when changes to the SRC_URI relate to
> changes in the output.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
I have similar patch in our poky trees. Also have patches
to export LICENSE and CVE_PRODUCT to buildhistory. These are used
by some post-build QA check scripts.
Acked-by: Mikko Rapeli <mikko.rapeli@bmw.de>
Cheers,
-Mikko
> ---
> meta/classes/buildhistory.bbclass | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/classes/buildhistory.bbclass b/meta/classes/buildhistory.bbclass
> index 0f26c3c..7d5e3eb 100644
> --- a/meta/classes/buildhistory.bbclass
> +++ b/meta/classes/buildhistory.bbclass
> @@ -116,6 +116,7 @@ python buildhistory_emit_pkghistory() {
> self.srcrev = ""
> self.layer = ""
> self.config = ""
> + self.src_uri = ""
>
>
> class PackageInfo:
> @@ -258,6 +259,7 @@ python buildhistory_emit_pkghistory() {
> rcpinfo.packages = packages
> rcpinfo.layer = layer
> rcpinfo.config = sortlist(oe.utils.squashspaces(d.getVar('PACKAGECONFIG') or ""))
> + rcpinfo.src_uri = oe.utils.squashspaces(d.getVar('SRC_URI') or "")
> write_recipehistory(rcpinfo, d)
>
> bb.build.exec_func("read_subpackage_metadata", d)
> @@ -368,6 +370,7 @@ def write_recipehistory(rcpinfo, d):
> f.write(u"PACKAGES = %s\n" % rcpinfo.packages)
> f.write(u"LAYER = %s\n" % rcpinfo.layer)
> f.write(u"CONFIG = %s\n" % rcpinfo.config)
> + f.write(u"SRC_URI = %s\n" % rcpinfo.src_uri)
>
> write_latest_srcrev(d, pkghistdir)
>
> --
> 1.8.3.1
>
>
>
>
next prev parent reply other threads:[~2020-10-26 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 4:03 [RFC PATCH 0/2] buildhistory: record SRC_URI Paul Eggleton
2020-10-19 4:03 ` [RFC PATCH 1/2] classes/buildhistory: " Paul Eggleton
2020-10-26 6:43 ` Mikko Rapeli [this message]
2020-10-28 14:21 ` [OE-core] " Richard Purdie
2020-10-29 9:18 ` Mikko Rapeli
2020-10-29 11:35 ` Richard Purdie
2020-10-19 4:03 ` [RFC PATCH 2/2] classes/buildhistory: also save recipe info for native recipes Paul Eggleton
2020-10-19 21:16 ` [OE-core] [RFC PATCH 0/2] buildhistory: record SRC_URI Paul Eggleton
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=20201026064259.GT2040@korppu \
--to=mikko.rapeli@bmw.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.microsoft.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