From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>,
"Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org
Subject: Re: BB_DANGLINGAPPENDS_WARNONLY = "1" or "true"?
Date: Mon, 04 Nov 2013 18:47:32 +0000 [thread overview]
Message-ID: <2613359.1lbv24R3Iq@helios> (raw)
In-Reply-To: <CAMKF1so3X0P=A5fvVpzj-3RMntH_bGVJsGX2iJFJoiFZgJyksQ@mail.gmail.com>
On Sunday 03 November 2013 12:49:16 Khem Raj wrote:
> On Sat, Nov 2, 2013 at 3:27 AM, Robert P. J. Day <rpjday@crashcourse.ca>
wrote:
> > (i can see it's going to be that kind of weekend.) ref manual reads:
> > BB_DANGLINGAPPENDS_WARNONLY = "1"
> >
> > but some layers define:
> >
> > meta-linaro/meta-aarch64/conf/layer.conf:BB_DANGLINGAPPENDS_WARNONLY =
> > "true"
> > meta-linaro/meta-linaro-toolchain/conf/layer.conf:BB_DANGLINGAPPENDS_WARN
> > ONLY = "true"
> > meta-linaro/meta-linaro/conf/layer.conf:BB_DANGLINGAPPENDS_WARNONLY =
> > "true"
> > poky-extras/meta-kernel-dev/conf/layer.conf:BB_DANGLINGAPPENDS_WARNONLY
> > ?= "true"
> >
> > so general question(s) -- is it understood that "1" and "true" are
> > equivalent? should there be a standard? should the ref manual be
> > enhanced, or should the above layers clean themselves up?
>
> They are all correct. Accepted values are
>
> "1", "yes", "true"
Note - for this variable only. For consistency with other "boolean" type
variables I'd suggest sticking to "1".
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-11-04 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 10:27 BB_DANGLINGAPPENDS_WARNONLY = "1" or "true"? Robert P. J. Day
2013-11-03 20:49 ` Khem Raj
2013-11-04 18:47 ` Paul Eggleton [this message]
2013-11-04 18:54 ` Robert P. J. Day
2013-11-04 19:02 ` Paul Eggleton
2013-11-04 19:29 ` Khem Raj
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=2613359.1lbv24R3Iq@helios \
--to=paul.eggleton@linux.intel.com \
--cc=raj.khem@gmail.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@yoctoproject.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.