From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Khem Raj <raj.khem@gmail.com>
Cc: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [PATCH] use weak assignments for PNBLACKLIST in recipe files
Date: Wed, 27 May 2020 15:50:01 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.2005271549080.7100@localhost.localdomain> (raw)
In-Reply-To: <CAMKF1sr85R8xasLrgaSfO_in12cKPFSqD+xEKZirSeHh1hugmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
On Wed, 27 May 2020, Khem Raj wrote:
>
>
> On Wed, May 27, 2020 at 3:14 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Tue, 26 May 2020, Khem Raj wrote:
>
> > On Mon, May 25, 2020 at 12:21 PM Robert P. J. Day <rpjday@crashcourse.ca>
> wrote:
> > >
> > > Make sure PNBLACKLIST assignments in recipe files use weak
> > > assignment, so they can be overridden in, for example, local.conf
> > > files.
> > >
> >
> > I would like contributions here when someone fixes one of the
> > blacklisted recipes. This patch will let downstream users host it in
> > bbappends or other places what is the intended use of this patch?
>
> i'm not sure what you're asking for here ... there is no claim that
> any of these recipes have been fixed in any way, only that weak
> assignment seems to be the default for blacklisting to at least allow
> for the possibility of overriding.
>
>
> Ok I think that’s fine I wanted to understand the reason since weak
> assignment do have some unintended results but if it is to make it
> uniform I Think that’s fair
discussion on YP list that inspired this:
https://lists.yoctoproject.org/g/yocto/topic/74460612#49479
rday
prev parent reply other threads:[~2020-05-27 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 19:21 [PATCH] use weak assignments for PNBLACKLIST in recipe files Robert P. J. Day
2020-05-26 23:18 ` [oe] " Khem Raj
2020-05-27 10:14 ` Robert P. J. Day
2020-05-27 19:09 ` Khem Raj
2020-05-27 19:50 ` Robert P. J. Day [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=alpine.LFD.2.21.2005271549080.7100@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@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 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.