On 5/2/23 4:25 AM, Niko Mauno wrote:
On 31.10.2022 18.23, Mark Hatle via lists.yoctoproject.org wrote:
There is a kirkstone-next branch. It is best effort. There likely will
never be a kirkstone branch, as we have no plans to officially support
Kirkstone.
(meta-xilinx and meta-xilinx-tools)
Feel free to contribute fixed or suggest backports from langdale/master
to kirkstone-next.
Likely the next LTS is when we will start to sync-up, but we're not
ready to make any commitments to this.
I suggest if you need kirkstone (LTS) support you work with an OSV to
support this work.
--Mark
Hello, FYI I've opened a pull request against meta-xilinx Github
repository's kirkstone-next branch:
https://github.com/Xilinx/meta-xilinx/pull/52 which helps to take
2022.2 release into use with LTS Yocto Kirkstone.
I have not had time to review it yet. I will get to this likely in a few days.
We're finishing up 2023.1 related work that is my immediate focus.
The reason I opened it against Github meta-xilinx repo instead of Yocto
project's meta-xilinx repo is the latter provides older 2022.1 release
whereas the former newer 2022.2 release
I would be curious if kirkstone-next branches support for 2022.2 release
is going to propagate also to YP meta-xilinx repo at some point?
I doubt it. We don't have any plans to support the kirkstone branch. This is
why it was only posted on github along with '-next'. The creation of this
branch was simply to make it easier for external users to have a starting point,
but it's unsupported.
We are currently working on supporting langdale and mickledore/master.
--Mark
-Niko
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5241):
https://lists.yoctoproject.org/g/meta-xilinx/message/5241
Mute This Topic: https://lists.yoctoproject.org/mt/94568772/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
