On 19 Oct 2022, at 07:34, Khem Raj via lists.openembedded.org <raj.khem=gmail....@lists.openembedded.org> wrote: > > On Tue, Oct 18, 2022 at 10:42 PM Alexander Kanavin > <alex.kana...@gmail.com> wrote: >> >> Can you show examples where this is needed? Custom variable does not seem a >> good idea. I also worry that it’ll break automated updates (it’s bad enough >> with mesa-gl, this might make it worse). > > https://github.com/ndechesne/meta-qcom/blob/master/recipes-graphics/mesa/mesa_git.bb
That is, well, horrible. *If* we’re going to expose a mesa.inc that people outside of core can use to package up their own random Mesa SHA then mesa.inc should just be the packaging logic. However, I don’t understand something about the patch. Why do we only need to apply it on native builds? It’s a backport from upstream, so should be the fix. If it breaks when applied to target builds, is there a bug upstream for that? Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171970): https://lists.openembedded.org/g/openembedded-core/message/171970 Mute This Topic: https://lists.openembedded.org/mt/94420106/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
