From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jonathan Liu <net147@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] image.bbclass: Do not expand variables in IMAGE_CMD vardepsexclude
Date: Mon, 12 Sep 2016 11:19:33 +0100 [thread overview]
Message-ID: <1473675573.20226.364.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160911121416.31304-1-net147@gmail.com>
On Sun, 2016-09-11 at 22:14 +1000, Jonathan Liu wrote:
> This fixes tashhash mismatch errors creating images when IMAGE_CMD
> references a variable whose value is always changing even though the
> variable is specified in IMAGE_CMD vardepsexclude.
>
> Signed-off-by: Jonathan Liu <net147@gmail.com>
> ---
> meta/classes/image.bbclass | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 8c8b8a2..f85ea86 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -441,6 +441,10 @@ python () {
> localdata.delVar('DATETIME')
> localdata.delVar('TMPDIR')
>
> + vardepsexclude = d.getVarFlag('IMAGE_CMD', 'vardepsexclude',
> True) or ''
> + vardepsexclude += ' ' + (d.getVarFlag('IMAGE_CMD_' + realt,
> 'vardepsexclude', True) or '')
> + for var in vardepsexclude.split():
> + localdata.delVar(var)
> image_cmd = localdata.getVar("IMAGE_CMD", True)
> vardeps.add('IMAGE_CMD_' + realt)
> if image_cmd:
I think this is complicating an already fragile situation and it
worries me. Can you be more specific about which variable is causing
problems here?
I'm starting to wonder if we should have an explicit flag set here for
"problem" variables and we'd default to the values "DATETIME TMPDIR"
which are already handled in the code. You'd then just need to extend
that value. Using vardepsexclude seems to partially but not completely
match?
Incidentally, I really want to complete some of the rework in this area
so we get to "proper" functions and can stop playing games like this. I
just haven't had the time to do that and this point in the release
cycle isn't the right time to do that.
Cheers,
Richard
next prev parent reply other threads:[~2016-09-12 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 12:14 [PATCH] image.bbclass: Do not expand variables in IMAGE_CMD vardepsexclude Jonathan Liu
2016-09-12 10:19 ` Richard Purdie [this message]
2016-09-12 14:05 ` Jonathan Liu
2016-09-12 16:43 ` Richard Purdie
2016-09-13 6:53 ` Jonathan Liu
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=1473675573.20226.364.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=net147@gmail.com \
--cc=openembedded-core@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.