Richard, Em sex., 27 de mar. de 2026 às 14:09, Richard Purdie via lists.openembedded.org <[email protected]> escreveu: > > On Thu, 2026-03-26 at 13:35 -0500, Randolph Sapp wrote: > > On Mon Mar 16, 2026 at 12:25 PM CDT, Randolph Sapp via > > lists.openembedded.org wrote: > > > On Fri Feb 27, 2026 at 12:31 PM CST, Randolph Sapp via > > > lists.openembedded.org wrote: > > > > From: Randolph Sapp <[email protected]> > > > > > > > > No functional changes. Just bumping PR to help with automated > > > > > > Hey Paul, have you gotten a chance to review this series yet? I've been > > > told you may have some comments. > > > > > > Randolph > > > > Has anyone gotten a chance to review this yet? > > Paul and Ross have some thoughts but we're basically still drowning in > the backlog of patch review. We're all frustrated about that. This one > is more Ross' area of expertise than mine so I'm waiting on that.I'm > replying since I do feel bad we've not got to this yet. > > I wish it were different, I'm doing what I can with various patches but > I'm also behind on review for several. > > The challenge with this patchset is it is a fairly invasive change, it > does inject a go dependency into a core part of our graphics stack and > as such, I think we're all quite nervous about it. It has taken a lot > of back and forth to pass the autobuilder's tests and that in itself is > a bit of a worry.
I understand the concern — this is an invasive change and caution is warranted for something that touches such a core part of the graphics stack. That said, I think it's worth recognizing that Randolph has been exceptionally persistent and responsive throughout this process. We're at v16 now, and every issue that has come up — from cgo reproducibility to busybox-init support to autobuilder failures — has been addressed. That level of commitment to getting it right speaks well for the long-term maintainability of this work. Regarding the Go dependency: Go support in OE-Core has a long history at this point and is well-maintained. I don't think introducing it as a dependency in the graphics stack is as risky as it might seem at first glance — we're not pulling in something experimental. The problems this series solves are real. The race conditions with weston-init and DRM device registration, the scripting sprawl around xserver-nodm-init — these are pain points that affect downstream users. emptty offers a clean, unified solution for both X11 and Wayland sessions. In my opinion, this patchset should go in. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#234106): https://lists.openembedded.org/g/openembedded-core/message/234106 Mute This Topic: https://lists.openembedded.org/mt/118035107/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
