From: Peter Seebach <peter.seebach@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/2] File inclusion and variable assignment tracking
Date: Wed, 20 Jun 2012 13:41:33 -0500 [thread overview]
Message-ID: <cover.1340217563.git.peter.seebach@windriver.com> (raw)
This is the assignment/inclusion tracking stuff I've had floating
around. In further testing, I found one missing [1] that made it
fail for "bitbake -e [specific package]". Haven't had any other
troubles with it.
This could totally use improvement, but I think this has reached a
point where:
1. It's more useful to have it than not.
2. It will be better improved by feedback from live usage.
Impact outside of the bitbake -e case is basically nil, and in the
-e case it's a HUGE improvement in usability.
The following changes since commit d316f28ed725ff40daa8771c1aa224ac46d5b224:
Richard Purdie (1):
methodpool: Improve method already seen error message
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/tracking
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/tracking
Peter Seebach (2):
data_smart.py: Provide (optional) logging of variable modifications
data_smart.py: Track configuration file inclusions
lib/bb/cooker.py | 2 +
lib/bb/data.py | 65 +++++++++++++++++-----
lib/bb/data_smart.py | 140 +++++++++++++++++++++++++++++++++++++--------
lib/bb/parse/__init__.py | 6 ++-
lib/bb/parse/ast.py | 65 ++++++++++++----------
5 files changed, 209 insertions(+), 69 deletions(-)
next reply other threads:[~2012-06-20 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 18:41 Peter Seebach [this message]
2012-06-20 18:41 ` [PATCH 1/2] data_smart.py: Provide (optional) logging of variable modifications Peter Seebach
2012-06-20 18:41 ` [PATCH 2/2] data_smart.py: Track configuration file inclusions Peter Seebach
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.1340217563.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.