bitbake-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: "enrico.scholz@sigma-chemnitz.de"
	<enrico.scholz@sigma-chemnitz.de>,
	Damian Wrobel <dwrobel@ertelnet.rybnik.pl>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] [PATCH] cooker: Only warn on potentially incompatible layer
Date: Wed, 8 Sep 2021 12:36:12 +0000	[thread overview]
Message-ID: <077e555a9d32412d83eedaa347a1eff4@axis.com> (raw)
In-Reply-To: <lyv93b9yr7.fsf@ensc-virt.intern.sigma-chemnitz.de>

> -----Original Message-----
> From: bitbake-devel@lists.openembedded.org <bitbake-
> devel@lists.openembedded.org> On Behalf Of Enrico Scholz via
> lists.openembedded.org
> Sent: den 8 september 2021 11:56
> To: Damian Wrobel <dwrobel@ertelnet.rybnik.pl>
> Cc: bitbake-devel@lists.openembedded.org
> Subject: Re: [bitbake-devel] [PATCH] cooker: Only warn on potentially
> incompatible layer
> 
> "Damian Wrobel" <dwrobel@ertelnet.rybnik.pl> writes:
> 
> > It frequently happens that the 3rd party layer is, in practise,
> > fully compatible with the older version of yocto. So, instead of
> > false positively reporting an error, it seems to be more
> > appropriately to just emit the warning.
> 
> You can achieve this already now (when you are really sure that it works
> for your bsp).  Just set
> 
> | LAYERSERIES_COMPAT:<foreign-layer>:append = " frodo"
> 
> in your bblayers.conf.

Minor detail: LAYERSERIES_COMPAT is among the variables that have 
not been changed to use the new override format, so the above should 
be:

LAYERSERIES_COMPAT_<foreign-layer>:append = " frodo"

> Enrico

//Peter


  reply	other threads:[~2021-09-08 12:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 14:28 [PATCH] cooker: Only warn on potentially incompatible layer Damian Wrobel
2021-09-03 17:07 ` [bitbake-devel] " Richard Purdie
2021-09-03 17:53   ` Damian Wrobel
2021-09-04  7:54     ` [bitbake-devel] " Richard Purdie
2021-09-05  8:40       ` Peter Kjellerstedt
2021-09-07  8:54       ` Damian Wrobel
2021-09-07 11:40         ` [bitbake-devel] " Richard Purdie
2021-09-07 13:50           ` Damian Wrobel
2021-09-07 13:57             ` Martin Jansa
2021-09-07 14:06             ` Alexander Kanavin
2021-09-07 15:35               ` Damian Wrobel
2021-09-07 15:49                 ` [bitbake-devel] " Alexander Kanavin
2021-09-07 16:38                   ` Damian Wrobel
2021-09-07 19:17                     ` [bitbake-devel] " Richard Purdie
2021-09-07 20:18                       ` Alexander Kanavin
2021-09-08  9:56 ` Enrico Scholz
2021-09-08 12:36   ` Peter Kjellerstedt [this message]
2021-09-08 13:35   ` Damian Wrobel

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=077e555a9d32412d83eedaa347a1eff4@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=dwrobel@ertelnet.rybnik.pl \
    --cc=enrico.scholz@sigma-chemnitz.de \
    /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;
as well as URLs for NNTP newsgroup(s).