Re: [RFC][yocto][meta-lts-mixins][kirkstone/go] Backport golang from master to kirkstone
Adrian Freihofer
Hi Alex, hi José
toggle quoted message
Show quoted text
The meta-lts-mixin layers for dunfell have a major disadvantage: Replacing the go tool-chain breaks more or less all recipes from meta- virtualization and potentially other layers. I think with go it should be possible to have a meta-lts-mixin layer which adds support for additional go versions instead of overriding the version provided by poky. That would potentially allow to use poky on the kirkstone branch and meta-virtualization on a newer branch on the long run. Would it be possible to add e.g. a copy of the go.bbclass as well as the go recipes from a recent poky version in a way it does not override the go stack provided by poky? As an example: Would it be possible to add a go1-19.bbclass to the meta-meta-lts-mixin layer? This would allow to add also a newer Docker recipe which inherits go1-19 instead of just go to the meta-lts-mixin layers without breaking anything from poky or meta-virtualization. I already tried to share my thoughts here: https://lists.openembedded.org/g/openembedded-core/message/178146?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Acreated%2C0%2Cgolang%2C20%2C2%2C0%2C97444547 Best regards, Adrian On Thu, 2023-03-30 at 12:08 +0200, Alexander Kanavin wrote:
I think I pushed the work directly to the respecitve branches in |
|