On Wed, Apr 17, 2024 at 2:00 AM Alexander Kanavin via lists.openembedded.org
wrote:
> On Tue, 16 Apr 2024 at 17:03, Martin Jansa wrote:
> > As there is strong opinion against declaring scarthgap compatibility
> > in official meta-python2 from Timo, Alex and Jose, I don't plan to
> > merge
On Tue, 16 Apr 2024 at 17:03, Martin Jansa wrote:
> As there is strong opinion against declaring scarthgap compatibility
> in official meta-python2 from Timo, Alex and Jose, I don't plan to
> merge Marek's change (nor my version with additional fixes for
> Upstream-Status etc).
There's more to
Target python recipes are already blacklisted since
https://github.com/shr-project/meta-python2/commit/10c65fc18998d302f34634ffceaf31ab335056dd
so meta-python2 already provides just python-native and necessary
bbclasses (as pythonnative.bbclass and few others).
So I don't want to add another
On Tue, 16 Apr 2024 at 16:19, Peter Marko via lists.openembedded.org
wrote:
> 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
-Original Message-
From: openembedded-devel@lists.openembedded.org
On Behalf Of Marek Vasut via
lists.openembedded.org
Sent: Tuesday, April 16, 2024 15:55
To: Martin Jansa
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-python2][PATCH] layer.conf: update
On Tue, 16 Apr 2024 at 15:55, Marek Vasut via lists.openembedded.org
wrote:
> 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
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
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
Yes to Tim's hard no. Qt5 itself is EOL for almost a year now (don't
tell me about their commercial offers, ok?).
I would put something similar to meta-gpl2 into that layer instead actually:
https://git.yoctoproject.org/meta-gplv2/commit/?id=43bf0e8d5985945d19d01f94bfbbda420c4435f3
Alex
On
This is a hard no from me.
On Mon, Apr 15, 2024 at 6:59 AM Marek Vasut via lists.openembedded.org
wrote:
> On 4/15/24 3:49 PM, Jose Quaresma wrote:
> > Hi Marek,
>
> Hi,
>
> > Last commit on this layer was done 2 years ago and it was at the time to
> > add Kirkstone compatibility, nothing more
On 4/15/24 3:49 PM, Jose Quaresma wrote:
Hi Marek,
Hi,
Last commit on this layer was done 2 years ago and it was at the time to
add Kirkstone compatibility, nothing more since then.
Python 2 is dead since 1/1/2020. That means that we (python dev) will not
improve it anymore after that day,
Hi Marek,
Last commit on this layer was done 2 years ago and it was at the time to
add Kirkstone compatibility, nothing more since then.
Python 2 is dead since 1/1/2020. That means that we (python dev) will not
improve it anymore after that day,
even if someone finds a security problem in it. You
Support both kirkstone and scarthgap as that seems to work well.
Signed-off-by: Marek Vasut
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index 38ef579..0f228ca 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@
13 matches
Mail list logo
