Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] boost: Convert ??= weaker assingment to weak ?= assignment
Date: Thu, 23 Jan 2014 08:43:29 -0800	[thread overview]
Message-ID: <5712962.WyPAeLeASC@leo> (raw)
In-Reply-To: <CABcZANk3D=dL=73=spKrnL-YeOmcxng1EN5ucQu0LD-O48Vd5g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]

On Thursday, January 23, 2014 09:31:47 AM Chris Larson wrote:
> On Wed, Jan 22, 2014 at 6:16 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > On Friday, December 06, 2013 05:42:26 PM Khem Raj wrote:
> > > ??= does not react at all with
> > > BOOST_LIBS += "${@base_contains('PACKAGECONFIG', 'python', 'python', '',
> > > d)}"
> > > 
> > > even though we have
> > > 
> > > PACKAGECONFIG ??= "" it does not honor it and always add python to
> > > BOOST_LIBS but the dependency is not added so it fails to build
> > > complaining for missing python headers which is a understood outcome
> > > 
> > > When converted to ?= it works as expected and only add --with-python
> > > in bjam when python is specified in PACKAGECONFIG otherwise not.
> > > 
> > > Is it a bitbake bug ? in anycase ?= should be enough of loose rope
> > > to let user/distro configure the packageconfig policy
> > 
> > OK so the problem is that I have meta-ros in my layer-mix and in that
> > layer
> > it defines PACKAGECONFIG ?= "python" IMO it should have appended instead
> > of
> > redefining. Thats why I was seeing what I was seeing.
> 
> It's worth noting that recipes, in general, should use ?= rather than ??=,
> but config files, in general, should use ??=. Otherwise it becomes
> impossible for the config metadata to define an overriding default -- the
> last ??= wins, after all, and that would always be the recipe. IMO default
> values in the recipe are there to give sane behavior when there's no
> configuration coming in from elsewhere, not to override configuration
> defaults.

yes I think thats a good point. so lets consider this patch for inclusion
now we know the reason, I can resubmit with proper subject and patch header

-- 
-Khem

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2014-01-23 16:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-07  1:42 [PATCH] boost: Convert ??= weaker assingment to weak ?= assignment Khem Raj
2013-12-08 21:36 ` Lukas Bulwahn
2013-12-09 11:48 ` Richard Purdie
2013-12-09 17:34   ` Khem Raj
2013-12-09 21:51     ` Richard Purdie
2013-12-09 23:11       ` Khem Raj
2013-12-10 10:32         ` Richard Purdie
2014-01-23  1:16 ` Khem Raj
2014-01-23 16:31   ` Chris Larson
2014-01-23 16:43     ` Khem Raj [this message]
2014-01-28 12:31       ` 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=5712962.WyPAeLeASC@leo \
    --to=raj.khem@gmail.com \
    --cc=clarson@kergoth.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox