From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [RFC PATCH 0/3] Tracking parsed configuration files
Date: Tue, 26 Jul 2011 21:46:08 -0700 [thread overview]
Message-ID: <cover.1311741742.git.josh@linux.intel.com> (raw)
All,
This series attempts to address Yocto bug 1246: "Configuration changes could
be saved to a file the cooker isn't using".
It's an ugly series and the issue will only present itself if users run the
UI trough alternative ways. My main issue is that we can't easily track all
loaded conf files at parseConfigurationFiles time so it feels a little
brittle.
Thoughts? Comments?
Regards,
Joshua
Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.
The following changes since commit 2650be190afc05f9472aca8b11af99205a342838:
ui/crumbs/tasklistmodel: fix loading a saved recipe (2011-07-26 09:42:28 -0700)
are available in the git repository at:
git://github.com/incandescant/bitbake configfiles
https://github.com/incandescant/bitbake/tree/configfiles
Joshua Lock (3):
cooker: track conf files parsed outside of the usual bitbake.conf
inclusion
cooker|event: notify if pre/post file in ConfigFilePathFound event
ui/crumbs/[hobeventhandler|configurator]: don't use unparsed files
lib/bb/cooker.py | 10 +++++++++-
lib/bb/event.py | 3 ++-
lib/bb/ui/crumbs/configurator.py | 8 ++++----
lib/bb/ui/crumbs/hobeventhandler.py | 6 ++++--
4 files changed, 19 insertions(+), 8 deletions(-)
--
1.7.6
next reply other threads:[~2011-07-27 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 4:46 Joshua Lock [this message]
2011-07-27 4:46 ` [RFC PATCH 1/3] cooker: track conf files parsed outside of the usual bitbake.conf inclusion Joshua Lock
2011-07-27 4:46 ` [RFC PATCH 2/3] cooker|event: notify if pre/post file in ConfigFilePathFound event Joshua Lock
2011-07-27 4:46 ` [RFC PATCH 3/3] ui/crumbs/[hobeventhandler|configurator]: don't use unparsed files Joshua Lock
2011-07-27 16:32 ` [RFC PATCH 0/3] Tracking parsed configuration files 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.1311741742.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox