From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/2] Store a list of parsed configuration files
Date: Tue, 2 Aug 2011 11:51:14 -0700 [thread overview]
Message-ID: <cover.1312310554.git.josh@linux.intel.com> (raw)
This series addresses Yocto #1246 "Configuration changes could be saved to a
file the cooker isn't using" by having the parser store a list of
configuration files it has parsed in the data object and then switching the
cooker to verify against this list that the found file was parsed before
emitting the ConfigFilePathFound event.
The following changes since commit 1009ca570a750a00b0e60afcc30ead070c7b310a:
hob: remove temporary directory on program shutdown (2011-07-30 12:21:18 -0700)
are available in the git repository at:
git://github.com/incandescant/bitbake configfiles
https://github.com/incandescant/bitbake/tree/configfiles
Joshua Lock (2):
bb/parse: track parsed configuration files in __BB_PARSED_CONF
bb/cooker: only emit ConfigFilePathFound for files which were parsed
lib/bb/cooker.py | 18 +++++++++++++++++-
lib/bb/parse/__init__.py | 12 +++++++++++-
lib/bb/parse/parse_py/ConfHandler.py | 2 ++
3 files changed, 30 insertions(+), 2 deletions(-)
--
1.7.6
next reply other threads:[~2011-08-02 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 18:51 Joshua Lock [this message]
2011-08-02 18:51 ` [PATCH 1/2] bb/parse: track parsed configuration files in __BB_PARSED_CONF Joshua Lock
2011-08-02 18:51 ` [PATCH 2/2] bb/cooker: only emit ConfigFilePathFound for files which were parsed Joshua Lock
2011-08-05 17:12 ` [PATCH 0/2] Store a list of parsed configuration files Richard Purdie
2011-08-05 18:07 ` Joshua Lock
2011-08-08 17:07 ` 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.1312310554.git.josh@linux.intel.com \
--to=josh@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 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.