Em seg., 1 de ago. de 2022 às 19:41, Richard Purdie <richard.purdie@...> escreveu: What about security flaws that aren't fixed and could lead to a compromised device and people not kno

Em seg., 1 de ago. de 2022 às 14:30, Alexander Kanavin <alex.kanavin@...> escreveu: I don't see problems with this and whoever wishes to support it, can easily override it.

Em seg., 25 de jul. de 2022 às 18:09, Konrad Weihmann <kweihmann@...> escreveu: If the user can disable this, using a variable inside local.conf, it is acceptable and helps people be aware the

Em seg., 25 de jul. de 2022 às 15:13, Alexander Kanavin <alex.kanavin@...> escreveu: I like the idea so users are aware of it.

Em qua., 28 de jul. de 2021 às 12:43, Richard Purdie <richard.purdie@...> escreveu: I believe your plan is good and given the new layers will work down to dunfell I see no big problems

Hello Richard, Em qui., 15 de jul. de 2021 às 10:56, Richard Purdie <richard.purdie@...> escreveu: If we don't do as a flag day we cannot drop old code from bitbake, so my vote goes to

Em qua., 16 de jun. de 2021 às 02:08, Chen Qi <Qi.Chen@...> escreveu: I really like the === proposal.

Hello Richard, Em ter., 15 de jun. de 2021 às 07:29, Richard Purdie <richard.purdie@...> escreveu: Having it resetting it might fix this use case but what if the _collie use case is a

Em qui., 10 de set. de 2020 às 16:51, Alexander Kanavin <alex.kanavin@...> escreveu: I support this for sure. I've been using Rust with Yocto Project for a while now and it does fit well to be i

Hello all, Em seg., 7 de set. de 2020 às 13:14, Richard Purdie <richard.purdie@...> escreveu: I second this and at least at O.S. Systems we've been using Docker containers to keep main

<richard.purdie@...> wrote: We made a https://github.com/Freescale/meta-freescale/blob/master/classes/machine-overrides-extender.bbclass which allow for one override to expland to a se

Sure; every change comes with a risk however if someone does not want any change they can lock their layer hashes. However, doing manual patches also comes with they own set of risk and limits. I thin

Agreed. Few project's I'd like to see more regular updates (following the stable branch) on the stable branches are: go mesa cmake libarchive systemd gstreamer1.0 Those has good and big comunities and

he also recipes. A DISTRO_FEATURES or a MACHINE_FEATURES? It seems more related to the machine.

I'd go for 2 and see how bad is it. So we can plan accordingly and see if it can be doable or not for 2.5 release.

One possible way to mitigate the issue is raising a big warning but failing completely. This makes clear that it may fail but does not enforce a manual action to continue.

The main question here is if we are going to keep OpenSSL 1.0 and 1.1 in parallel inside OE-Core or not. For Pyro I think we should stay on 1.0 or have 1.1 as an opt-in option, but for 2.4 I would say

<alexander.kanavin@...> wrote: In fact not; as you generate the recipes for the dependencies, it goes recursively and is always good. Well we initially thought this would suffice but consi

Hello Alexander, <alexander.kanavin@...> wrote: When integrating the CHICKEN Scheme support onto the Yocto Project we dealt it using their installation tool but making the package of indiv

The requirement of membership for patchwork is non-sense. It is hosted under openembedded.org domain and as such it is a community resource. YP Git, CI and whatever is inside YP resources I am fine wi