All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adrian Bunk" <bunk@stusta.de>
To: Andrey Zhizhikin <andrey.z@gmail.com>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	Steve Sakoman <sakoman@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	Denys Dmytriyenko <denis@denix.org>,
	Joshua Watt <jpewhacker@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	"jdmason@kudzu.us" <jdmason@kudzu.us>,
	Khem Raj <raj.khem@gmail.com>
Subject: Re: [OE-core][PATCH 0/4] Import recipes from meta-python
Date: Sun, 17 May 2020 16:22:45 +0300	[thread overview]
Message-ID: <20200517132245.GA9940@localhost> (raw)
In-Reply-To: <CAHtQpK4AH08zQ6dx1OWjCR6WwAmrLHNZuz0O1O9WqUnBHNk2Pg@mail.gmail.com>

On Sat, May 16, 2020 at 10:24:04PM +0200, Andrey Zhizhikin wrote:
> On Sat, May 16, 2020 at 10:10 PM Adrian Bunk <bunk@stusta.de> wrote:
> >
> > On Sat, May 16, 2020 at 07:54:32PM +0000, Peter Kjellerstedt wrote:
> > > >
> > > > meta-openembedded/meta-python has a higher layer priority than OE-core.
> > > >
> > > > Adding higher upstream versions of these recipes to a lower-priority
> > > > layer in a stable series is a potential source for weird problems.
> > >
> > > I would assume they'd be removed from meta-python at the same time
> > > they are added to meta.
> >
> > "at the same time" is complicated since OE-core has releases,
> > but meta-openembedded is just a branch.
> >
> > I would also assume that not all users of stable series are updating
> > meta-openembedded to the latest on the dunfell branch at the same
> > time as OE-core, some users might end up updating one but never
> > updating the other one.
> 
> That I believe would be a terrible mistake when people opt-in to take
> a layer, but never care about updating it... :(

The typical Yocto user starts with whatever prehistoric Yocto release 
came with the BSP distribution for the reference hardware, and then 
develops a new product on top of that.

I would not be surprised if someone will have the initial Yocto 2.7
release, but uses the latest from the corresponding  meta-openembedded 
branch on top.

> On the contrary, a quick run of "bitbake-layers show-overlayed"
> exhibits the following on the [master] of both OE-Core and

Thanks a lot for this.

> meta-openembedded:
> =================
> python3-cython:
>   meta-python          0.29.14
>   meta                 0.29.16
> python3-dbusmock:
>   meta-python          0.16.7
>   meta                 0.19
> python3-docutils:
>   meta-python          0.15.2
>   meta                 0.16
> python3-pyparsing:
>   meta-python          2.4.6
>   meta                 2.4.7
> =================

I'll take care of getting these removed from meta-openembedded.

> Judging be versions, it looks like OE-Core recipes are maintained, but
> in meta-openembedded they are left on the side...

python3-docutils is ouch, since this problem is also in dunfell.

On a more positive note 0.16 is already in OE-core in the initial
Yocto 3.1 release, so removing it from meta-openembedded will only
be like a 0.15.2 -> 0.16 upgrade for some users but cannot result
in losing the recipe in weird layer combinations.

> Regards,
> Andrey.

cu
Adrian

  parent reply	other threads:[~2020-05-17 13:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 21:04 [OE-core][PATCH 0/4] Import recipes from meta-python Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 1/4] pycryptodome: Import " Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 2/4] pyelftools: " Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 3/4] python3-pycryptodome(x): Upgrade 3.9.4 -> 3.9.7 Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 4/4] python3-pyelftools: Upgrade 0.25 -> 0.26 Joshua Watt
2020-05-15 18:53 ` [OE-core][PATCH 0/4] Import recipes from meta-python Denys Dmytriyenko
2020-05-15 19:05   ` Richard Purdie
2020-05-15 19:12     ` Joshua Watt
2020-05-15 19:26       ` Denys Dmytriyenko
2020-05-15 19:56         ` Andrey Zhizhikin
2020-05-15 19:32       ` Khem Raj
2020-05-17  1:05         ` Alejandro Hernandez
2020-05-16  1:21     ` Steve Sakoman
2020-05-16 17:47       ` Adrian Bunk
2020-05-16 19:54         ` Peter Kjellerstedt
2020-05-16 20:09           ` Adrian Bunk
2020-05-16 20:24             ` Andrey Zhizhikin
2020-05-16 23:15               ` Andre McCurdy
2020-05-17 13:22               ` Adrian Bunk [this message]
2020-05-17 13:56                 ` Martin Jansa
2020-05-17 15:45                   ` Adrian Bunk
2020-05-17 16:00                     ` Martin Jansa
2020-05-17 16:14                       ` Adrian Bunk
2020-05-17 23:47                         ` Khem Raj
2020-05-19 18:20                           ` Steve Sakoman
2020-05-19 18:24                             ` Martin Jansa
2020-05-19 19:57                               ` Andre McCurdy
2020-05-21  9:11                                 ` Martin Jansa
2020-05-17 23:45                     ` Khem Raj
2020-05-17 23:41                 ` Khem Raj
2020-05-18  6:41                   ` Alejandro Hernandez
2020-05-17 23:38             ` Khem Raj

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=20200517132245.GA9940@localhost \
    --to=bunk@stusta.de \
    --cc=andrey.z@gmail.com \
    --cc=denis@denix.org \
    --cc=jdmason@kudzu.us \
    --cc=jpewhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=sakoman@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.