From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 2/3] Hob: Fix advanced setting reparse mechanism
Date: Mon, 19 Mar 2012 13:18:33 -0700 [thread overview]
Message-ID: <4F679499.3040105@linux.intel.com> (raw)
In-Reply-To: <817e7641f1d1df38a4233addbb454a3280576da6.1331887394.git.dongxiao.xu@intel.com>
On 16/03/12 01:48, Dongxiao Xu wrote:
> When judging if reparse is needed when change values in advanced
> setting, we need also include user's own defined variable pairs.
>
> [YOCTO #2121]
>
> Signed-off-by: Dongxiao Xu<dongxiao.xu@intel.com>
Signed-off-by: Joshua Lock <josh@linux.intel.com>
> ---
> lib/bb/ui/crumbs/hig.py | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/lib/bb/ui/crumbs/hig.py b/lib/bb/ui/crumbs/hig.py
> index 67cc94e..8d73d5f 100644
> --- a/lib/bb/ui/crumbs/hig.py
> +++ b/lib/bb/ui/crumbs/hig.py
> @@ -453,6 +453,8 @@ class AdvancedSettingDialog (CrumbsDialog):
> self.variables["PACKAGE_FORMAT"] = self.configuration.curr_package_format
> self.variables["INCOMPATIBLE_LICENSE"] = self.configuration.incompat_license
> self.variables["IMAGE_FSTYPES"] = self.configuration.image_fstypes
> + for key in self.configuration.extra_setting.keys():
> + self.variables[key] = self.configuration.extra_setting[key]
> self.md5 = hashlib.md5(str(sorted(self.variables.items()))).hexdigest()
> self.settings_changed = False
>
--
Joshua '贾詡' Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-19 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 8:48 [PATCH 0/3][PULL] Hob: Bug fix Dongxiao Xu
2012-03-16 8:48 ` [PATCH 1/3] Hob: reset the selection if switch to a new base image Dongxiao Xu
2012-03-19 20:18 ` Joshua Lock
2012-03-16 8:48 ` [PATCH 2/3] Hob: Fix advanced setting reparse mechanism Dongxiao Xu
2012-03-19 20:18 ` Joshua Lock [this message]
2012-03-16 8:48 ` [PATCH 3/3] Hob: save CONF_VERSION and LCONF_VERSION into template Dongxiao Xu
2012-03-19 20:18 ` Joshua Lock
2012-03-20 14:40 ` [PATCH 0/3][PULL] Hob: Bug fix 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=4F679499.3040105@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