Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/3] Improve bitbake-dumpsig
Date: Sat, 11 Mar 2017 06:22:14 +0100	[thread overview]
Message-ID: <cover.1489209703.git.pkj@axis.com> (raw)

This adds support to bitbake-dumpsig to specify the signature file to
dump by specifying a recipie and task using --task (-t), the same way
it is possible to do for bitbake-diffsigs.

It also adds support to bitbake-dumpsig and bitbake-diffsigs to output
some debug data (currently the names of the identified signature
files) by specifying --debug (-D).

//Peter

The following changes since commit 760e81678cec80dcdaab12c2a0a0148e3e0ba275:

  go: Add recipes for golang compilers and tools (2017-03-10 15:51:55 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib pkj/bitbake-dumpsig
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/bitbake-dumpsig

Peter Kjellerstedt (3):
  bitbake-dumpsig: Allow recipe and task to be specified
  bitbake-dumpsig: Add debug support
  bitbake-diffsigs: Add debug support

 bitbake/bin/bitbake-diffsigs |  9 +++++++
 bitbake/bin/bitbake-dumpsig  | 61 ++++++++++++++++++++++++++++++++++++--------
 2 files changed, 59 insertions(+), 11 deletions(-)

-- 
2.12.0



             reply	other threads:[~2017-03-11  5:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11  5:22 Peter Kjellerstedt [this message]
2017-03-11  5:22 ` [PATCH 1/3] bitbake-dumpsig: Allow recipe and task to be specified Peter Kjellerstedt
2017-03-11  5:22 ` [PATCH 2/3] bitbake-dumpsig: Add debug support Peter Kjellerstedt
2017-03-11  5:22 ` [PATCH 3/3] bitbake-diffsigs: " Peter Kjellerstedt

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.1489209703.git.pkj@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=bitbake-devel@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