From: "Khem Raj" <raj.khem@gmail.com>
To: Adrian Bunk <bunk@stusta.de>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: 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>
Subject: Re: [OE-core][PATCH 0/4] Import recipes from meta-python
Date: Sun, 17 May 2020 16:38:51 -0700 [thread overview]
Message-ID: <37d4502f-bd17-38cd-6abc-c327fe295def@gmail.com> (raw)
In-Reply-To: <20200516200957.GA8056@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1853 bytes --]
On 5/16/20 1:09 PM, Adrian Bunk 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.
>
You bring an interesting point. while the oe-core release tags are
driven by Yocto release cadence which has point release schedules,
OE-Core in itself does not have its release mechanism besides creating
and maintaining the branch. because oe-core independently is just a repo
you will need bitbake repo atleast to build something and bitbake has
its own release cadence.
> 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.
Thats very likely, although not preferred, most of products just freeze
these layers and do tweaking in their own layers because they have
control over them, where as they dont have much control over the
upstream layers. Its common with all third party and OSS projects.
So, if someone is basing their distro on oe-core + bitbake + meta-oe and
more then I would think they should be aware of these kind of changes
but I also think this could create some unexpected behaviour. Ideally
these recipes should be updated in meta-python to latest and same moved
to oe-core, then the move does not have to be atomic.
>
>> //Peter
>
> cu
> Adrian
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
prev parent reply other threads:[~2020-05-17 23:39 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
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 [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=37d4502f-bd17-38cd-6abc-c327fe295def@gmail.com \
--to=raj.khem@gmail.com \
--cc=bunk@stusta.de \
--cc=denis@denix.org \
--cc=jdmason@kudzu.us \
--cc=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox