From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <josh@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [RFC PATCH 0/3] Tracking parsed configuration files
Date: Wed, 27 Jul 2011 17:32:11 +0100 [thread overview]
Message-ID: <1311784331.2344.406.camel@rex> (raw)
In-Reply-To: <cover.1311741742.git.josh@linux.intel.com>
On Tue, 2011-07-26 at 21:46 -0700, Joshua Lock wrote:
> 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?
Likely bitbake should be maintaining a list of files the given parsing
process has included up to a given point. I believe we already have
something along those lines and might just want to expose it...
Cheers,
Richard
prev parent reply other threads:[~2011-07-27 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 4:46 [RFC PATCH 0/3] Tracking parsed configuration files Joshua Lock
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 ` Richard Purdie [this message]
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=1311784331.2344.406.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=josh@linux.intel.com \
/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