From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: RFC: Override expansion - changing the behaviour
Date: Tue, 07 Jun 2011 15:10:03 -0700 [thread overview]
Message-ID: <1307484603.15327.16.camel@scimitar> (raw)
In-Reply-To: <1306882804.27470.402.camel@rex>
On Wed, 2011-06-01 at 00:00 +0100, Richard Purdie wrote:
> Currently if you do:
>
> OVERRIDES = "z"
> DEPENDS_prepend = "a "
> DEPENDS = "b"
> DEPENDS_z = "c"
>
> d.update_data()
> d.getVar("DEPENDS") gives "a c"
> d.update_data()
> d.getVar("DEPENDS") gives "c"
>
> I'm proposing we should change the bitbake behaviour such that at the
> time bitbake expands the DEPENDS_z override, it removes "DEPENDS_z" from
> the data store.
FWIW I think this change is absolutely the right thing to do. The
current behaviour always catches me out (and I hope I'm not alone) and
changing it as suggested makes the behaviour much less surprising.
Cheers,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-07 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 23:00 RFC: Override expansion - changing the behaviour Richard Purdie
2011-06-01 14:59 ` Richard Purdie
2011-06-01 15:51 ` Chris Larson
2011-06-07 22:10 ` Joshua Lock [this message]
2011-06-07 22:16 ` Mark Hatle
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=1307484603.15327.16.camel@scimitar \
--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 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.