Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/5] Refactoring + improve bitbake-diffsigs
Date: Mon, 27 Aug 2012 21:44:30 +0100	[thread overview]
Message-ID: <cover.1346099795.git.paul.eggleton@linux.intel.com> (raw)

Refactor out a class which can be used as the basis for bitbake-based
utilities, and use it to improve bitbake-diffsigs to enable easily
specifying a recipe and task and determine what the difference was in
the signature data between the last two executions.

This change requires some support code within the metadata (since
BitBake itself knows nothing about the implementation of shared state);
a patch to implement this in OE-Core has been sent to the OE-Core
mailing list.

Note that this is similar in spirit but does not directly overlap with
Robert's bitbake-whatchanged script - that allows you to determine what
will be done before it happens, whereas this tool is useful for
determining why a rebuild occurred afterwards.


The following changes (against poky, but apply cleanly with -p2 against 
bitbake master) are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib paule/bbdiffsigs
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bbdiffsigs

Paul Eggleton (5):
  tinfoil: create simple interface for bitbake-based utilities
  lib/bb/siggen: replace tabs with spaces
  lib/bb/siggen.py: insert a colon between class and recipe name
  lib/bb/siggen.py: make signature dump/compare functions return a list
  bitbake-diffsigs: allow specifying task & follow deps recursively

 bitbake/bin/bitbake-diffsigs |   96 ++++++++++++++++++++++++++-
 bitbake/bin/bitbake-dumpsig  |    4 +-
 bitbake/bin/bitbake-layers   |  146 ++++++++++++++----------------------------
 bitbake/lib/bb/siggen.py     |  109 +++++++++++++++++--------------
 bitbake/lib/bb/tinfoil.py    |   98 ++++++++++++++++++++++++++++
 5 files changed, 301 insertions(+), 152 deletions(-)
 create mode 100644 bitbake/lib/bb/tinfoil.py

-- 
1.7.9.5




             reply	other threads:[~2012-08-27 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 20:44 Paul Eggleton [this message]
2012-08-27 20:44 ` [PATCH 1/5] tinfoil: create simple interface for bitbake-based utilities Paul Eggleton
2012-08-27 20:44 ` [PATCH 2/5] lib/bb/siggen: replace tabs with spaces Paul Eggleton
2012-08-27 20:44 ` [PATCH 3/5] lib/bb/siggen.py: insert a colon between class and recipe name Paul Eggleton
2012-08-27 20:44 ` [PATCH 4/5] lib/bb/siggen.py: make signature dump/compare functions return a list Paul Eggleton
2012-08-27 20:44 ` [PATCH 5/5] bitbake-diffsigs: allow specifying task & follow deps recursively Paul Eggleton
2012-09-07 11:09 ` [PATCH 0/5] Refactoring + improve bitbake-diffsigs 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.1346099795.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.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