<div dir="ltr">X might and likely will start to bitrot sooner for those not using RHEL 8 and its very conservative and never changing software stack. I can imagine Red Hat has no interest in supporting it on Fedora going forward for instance, they'll just make Xwayland work, and rip the standalone server and its drivers and libraries out. <div><br></div><div>Oe-core will have X for as long as the burden of fixing build errors and runtime issues with custom patches is not too painful. The point I am trying to make is that I am not convinced oe-core needs a 'real' ui at all, and opinion to the contrary should justify the need.<div><br></div><div><div>Alex</div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 11 Feb 2020 at 15:13, Adrian Bunk <<a href="mailto:bunk@stusta.de">bunk@stusta.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">On Tue, Feb 11, 2020 at 03:01:20PM +0100, Alexander Kanavin wrote:<br>
> Specifically (sorry for the rapid-followup), I think the main value<br>
> proposition of core is integration and testing of various language<br>
> toolchains and core libraries. UIs in embedded space can mean pretty much<br>
> anything, and so I'd leave that to specialised layers.<br>
<br>
That's actually quite different from your original email.<br>
<br>
Your original email raised the problem that X might start to bitrot<br>
after the end of support for RHEL 8 in the year 2029 (sic).<br>
<br>
What functionality should be in core for users/demo/QA/...<br>
is not strictly related to X versus Wayland.<br>
<br>
> Alex<br>
<br>
cu<br>
Adrian<br>
</blockquote></div>