From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Allow oe-pkgdata-util package-info to display more info
Date: Tue, 16 May 2017 12:56:18 +0200 [thread overview]
Message-ID: <cover.1494932131.git.pkj@axis.com> (raw)
After a build in our autobuilder, we use `oe-pkgdata-util package-info
-f package.manifest` to store a file with information about each
installed package. This is typically used to compare builds later
on. Since not every difference to a package is explained by its
version, we have found it beneficial to also include the SRC_URI in
the generated file.
This patch set adds SRC_URI to the pkgdata that is stored for each
package, and adds a new option to oe-pkgdata-util package-info,
-e <var>, that can be used to display extra variables from the
pkgdata.
//Peter
The following changes since commit 0fcbb4d0ec26ef24db78190dcdc5568af3beaa14:
GNU_MIRROR: switch from ftp to https (2017-05-11 16:56:00 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib pkj/oe-pkgdata-util_extra
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/oe-pkgdata-util_extra
Peter Kjellerstedt (2):
package.bbclass: Add SRC_URI to pkgdata
oe-pkgdata-util: package-info: Allow extra variables to be displayed
meta/classes/package.bbclass | 1 +
scripts/oe-pkgdata-util | 11 +++++++++--
2 files changed, 10 insertions(+), 2 deletions(-)
--
2.12.0
next reply other threads:[~2017-05-16 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 10:56 Peter Kjellerstedt [this message]
2017-05-16 10:56 ` [PATCH 1/2] package.bbclass: Add SRC_URI to pkgdata Peter Kjellerstedt
2017-05-16 10:56 ` [PATCH 2/2] oe-pkgdata-util: package-info: Allow extra variables to be displayed Peter Kjellerstedt
2017-05-16 13:14 ` [PATCH 0/2] Allow oe-pkgdata-util package-info to display more info Richard Purdie
2017-05-16 16:29 ` Peter Kjellerstedt
2017-05-23 13:38 ` Peter Kjellerstedt
2017-05-24 22:28 ` Richard Purdie
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=cover.1494932131.git.pkj@axis.com \
--to=peter.kjellerstedt@axis.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