A) Some layers only switch to an official branch name when the find a reason
to. E.g. branch "sumo" is created on openembedded-core but meta-A
keeps working on master unless an incompatible change is created in
openembedded-core that forces meta-A to create a "sumo" branch.
B) Other layers create
On Fri, 2018-04-06 at 10:16 -0400, Trevor Woerner wrote:
> A) Some layers only switch to an official branch name when the find a
> reason to. E.g. branch "sumo" is created on openembedded-core but
> meta-A keeps working on master unless an incompatible change is
> created in openembedded-core that
We have this variable appearing in a couple manuals BTW. If anyone has any
feedback on what is being said here I can update.
Thanks,
Scott
https://www.yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#var-LAYERSERIES_COMPAT
https://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html#crea
FWIW: I've updated some layers with this LAYERSERIES_COMPAT_ today
and I think it's good idea.
It probably won't be enough to stop questions like this:
http://lists.openembedded.org/pipermail/openembedded-core/2018-April/149696.html
but it's still better to show warning first and then some often
I understand the need to reduce the support burden. But there are some valid
cases when you want to use components/layers from a different set of releases.
It can sometimes be an older component in otherwise newer setup (i.e. one
layer hasn't been updated yet from rocko, but it still works fine
Shouldn't Master get all these changes first then we switch to stable
branch when we have a new release?
My German genes are raging about "Rules" ; )
- armin
On 04/06/2018 08:29 AM, Richard Purdie wrote:
> On Fri, 2018-04-06 at 10:16 -0400, Trevor Woerner wrote:
>> A) Some layers only switch to
On Fri, 2018-04-06 at 14:58 -0400, Denys Dmytriyenko wrote:
> I understand the need to reduce the support burden. But there are
> some valid
> cases when you want to use components/layers from a different set of
> releases.
>
> It can sometimes be an older component in otherwise newer setup (i.e
On Fri, 2018-04-06 at 13:46 -0700, akuster808 wrote:
> Shouldn't Master get all these changes first then we switch to stable
> branch when we have a new release?
>
> My German genes are raging about "Rules" ; )
master did get them?
To be really clear, "master" is never a value that would appear
On Fri, 2018-04-06 at 20:25 +0200, Martin Jansa wrote:
> FWIW: I've updated some layers with this LAYERSERIES_COMPAT_
> today and I think it's good idea.
Thanks. I know its late in the cycle but I think it will help.
> It probably won't be enough to stop questions like this:
> http://lists.openem
On Fri, 2018-04-06 at 11:16 -0700, Scott Rifenbark wrote:
> We have this variable appearing in a couple manuals BTW. If anyone
> has any feedback on what is being said here I can update.
Some small suggested tweaks:
"Using the LAYERSERIES_COMPAT variable makes it clear when a given
layer is unma
Thanks Richard
https://www.yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#var-LAYERSERIES_COMPAT
Scott
On Fri, Apr 6, 2018 at 3:25 PM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Fri, 2018-04-06 at 11:16 -0700, Scott Rifenbark wrote:
> > We have this variable appe
On Fri, 2018-04-06 at 15:44 -0700, Scott Rifenbark wrote:
> Thanks Richard
>
> https://www.yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#var-
> LAYERSERIES_COMPAT
Can you tweak:
"Lists the versions of the OpenEmbedded Core project"
->
"Lists the versions of OpenEmbedded-Core"
we woul
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 do
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 b
14 matches
Mail list logo