From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tom Rini <tom.rini@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] image.bbclass: Ensure IMAGE_FSTYPES is fully evaluated before live/live logic
Date: Sat, 28 Jun 2014 09:35:09 +0100 [thread overview]
Message-ID: <1403944509.28648.26.camel@ted> (raw)
In-Reply-To: <20140627151709.GU9006@bill-the-cat>
On Fri, 2014-06-27 at 11:17 -0400, Tom Rini wrote:
> On Fri, Jun 27, 2014 at 03:54:30PM +0100, Richard Purdie wrote:
> > I wondered about that but I did already check and:
> >
> > http://git.yoctoproject.org/cgit.cgi/poky/tree/bitbake/lib/bb/utils.py
> >
> > def contains(variable, checkvalues, truevalue, falsevalue, d):
> > val = d.getVar(variable, True)
> >
> > so it is being expanded afaict...
>
> Yeah, but what does that expand back to? My bitbake internals-fu is
> weak, but:
> $ git grep def\ getVar
> lib/bb/command.py: def getVariable(self, command, params):
> lib/bb/data.py:def getVar(var, d, exp = 0):
> lib/bb/data.py:def getVarFlag(var, flag, d):
> lib/bb/data.py:def getVarFlags(var, d):
> lib/bb/data_smart.py: def getVar(self, var, expand=False, noweakdefault=False
> lib/bb/data_smart.py: def getVarFlag(self, var, flag, expand=False, noweakdef
> lib/bb/data_smart.py: def getVarFlags(self, var, expand = False, internalflag
>
> So where do we map back to a 'getVar' that takes expand as arg 2 not arg
> 3?
Its calling:
lib/bb/data_smart.py: def getVar(self, var, expand=False, noweakdefault=False
since d is a data store object which becomes "self", the first argument
and the other two are then passed in with expand = True.
The bb.data.getVar(d, var, expand) syntax is just clumsy and deprecated
when you can write the same thing as d.getVar(var, expand).
Cheers,
Richard
prev parent reply other threads:[~2014-06-28 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 12:27 [PATCH] image.bbclass: Ensure IMAGE_FSTYPES is fully evaluated before live/live logic Tom Rini
2014-06-26 17:25 ` Otavio Salvador
2014-06-27 12:42 ` Tom Rini
2014-06-27 13:11 ` Otavio Salvador
2014-06-27 13:40 ` Richard Purdie
2014-06-27 14:16 ` Tom Rini
2014-06-27 14:54 ` Richard Purdie
2014-06-27 15:17 ` Tom Rini
2014-06-28 8:35 ` 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=1403944509.28648.26.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.rini@gmail.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