-----Original Message----- From: [email protected] <[email protected]> On Behalf Of Marek Vasut via lists.openembedded.org Sent: Tuesday, April 16, 2024 15:55 To: Martin Jansa <[email protected]> Cc: [email protected] Subject: Re: [oe] [meta-python2][PATCH] layer.conf: update LAYERSERIES_COMPAT for scarthgap
> On 4/15/24 7:48 PM, Martin Jansa wrote: > > If you need it just for some experiments than feel free to use: > > https://github.com/shr-project/meta-python2/commits/jansa/master/ > > which I've already updated (for built time benchmark which > > historically included qtwebengine as well > > https://github.com/shr-project/test-oe-build-time). > > > > But for anything more serious work with your customer to switch to > > something more supported, there are still minor upgrades to meta-qt5 > > (last in https://github.com/meta-qt5/meta-qt5/pull/556), but it's a > > dead end and switch to something else should have higher priority than > > switch to scarthgap (e.g. switching to meta-qt6). > > I am aware of qt5 being a dead end, but I also think if making this stuff > build with scarthgap is a one-liner change, I don't really see why not enable > people to build it. > > The security implications have to be considered by the users. Maybe this > should also be spelled out in the README, for both the meta-python2 and > meta-qt5. I can send such a patch ? Following works for yocto kirkstone + meta-lts-mixin kirkstone/go + meta-lts-mixin kirkstone/rust + meta-virtualization master LAYERSERIES_COMPAT_virtualization-layer += "kirkstone" meta-qt5 should be able to do something similar with meta-python2 if meta-python2 is frozen...
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#109980): https://lists.openembedded.org/g/openembedded-devel/message/109980 Mute This Topic: https://lists.openembedded.org/mt/105535514/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
