From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Trevor Woerner <twoerner@gmail.com>
Cc: Alexander Kanavin <alexander.kanavin@intel.com>,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] LAYERSERIES
Date: Sun, 15 Apr 2018 22:12:29 +0100 [thread overview]
Message-ID: <1523826749.2942.358.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180414214812.GA25986@linux-uys3>
On Sat, 2018-04-14 at 17:48 -0400, Trevor Woerner wrote:
> On Fri 2018-04-06 @ 10:56:53 PM, Richard Purdie wrote:
> >
> > To be really clear, "master" is never a value that would appear in
> > LAYERSERIES. That would let everyone be lazy and master would match
> > everywhere, then this would all be pointless.
> So what happens when the master branch of a BSP layer doesn't work
> with the
> last release, but bitbake hasn't been updated with the next release's
> name?
>
> I.e. the sumo branch of meta-bsp has
>
> LAYERSERIES_COMPAT_bsp = "sumo"
>
> but what am I supposed to put as the value when meta-bsp's master
> branch
> becomes incompatible with sumo? "master" is not allowed, and "thud"
> fails too.
>
> At some point between one release and the next something might/will
> break. In
> which case the only thing a BSP's master branch will work with is
> openembedded-core's master.
Post release of sumo we'll add thud as a possible option to OE-Core and
things should be ok?
Cheers,
Richard
next prev parent reply other threads:[~2018-04-15 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 10:37 LAYERSERIES Richard Purdie
2018-04-06 14:16 ` [Openembedded-architecture] LAYERSERIES Trevor Woerner
2018-04-06 15:29 ` Richard Purdie
2018-04-06 18:16 ` Scott Rifenbark
2018-04-06 22:25 ` Richard Purdie
2018-04-06 22:44 ` Scott Rifenbark
2018-04-07 14:13 ` Richard Purdie
2018-04-06 18:25 ` Martin Jansa
2018-04-06 22:00 ` Richard Purdie
2018-04-06 20:46 ` akuster808
2018-04-06 21:56 ` Richard Purdie
2018-04-14 21:48 ` Trevor Woerner
2018-04-15 21:12 ` Richard Purdie [this message]
2018-04-06 18:58 ` Denys Dmytriyenko
2018-04-06 21:52 ` 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=1523826749.2942.358.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@intel.com \
--cc=openembedded-architecture@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@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.