All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: should layers define BB_DANGLINGAPPENDS_WARNONLY ?= "1"?
Date: Mon, 2 Nov 2015 11:03:37 -0700	[thread overview]
Message-ID: <5637A579.6040808@mlbassoc.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1511021251410.10363@localhost>

On 2015-11-02 10:54, Robert P. J. Day wrote:
>
>    perusing the meta-musl layer, and noticed in layer.conf the line:
>
> BB_DANGLINGAPPENDS_WARNONLY ?= "1"
>
> i thought this was a bit odd since (at least to me) it seems like the
> sort of thing a *developer* might set in their local.conf to
> temporarily deal with a dangling .bbappend file -- it never occurred
> to me that it would be appropriate for a layer to define that value
> itself as an inherent part of its own ... layerness.
>
>    a quick grep of the couple dozen layers i have checked out revealed
> two layers that do that:
>
> ./meta-musl/conf/layer.conf:BB_DANGLINGAPPENDS_WARNONLY ?= "1"
> ./meta-yocto-kernel-extras/meta-kernel-dev/conf/layer.conf:BB_DANGLINGAPPENDS_WARNONLY
> ?= "true"
>
>    i'm curious what others think of this approach.

Sounds dangerous, bordering on incorrect (or irresponsible) to me.
This could easily mask a problem and is not layer specific, i.e.
the warning would then apply to all layers, not just meta-musl.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  parent reply	other threads:[~2015-11-02 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 17:54 should layers define BB_DANGLINGAPPENDS_WARNONLY ?= "1"? Robert P. J. Day
2015-11-02 18:01 ` Paul Eggleton
2015-11-02 18:03 ` Gary Thomas [this message]
2015-11-02 21:37 ` Khem Raj
2015-11-03 11:15   ` Robert P. J. Day

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=5637A579.6040808@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --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.