<div><div dir="auto">But shouldn’t you take it all the way upstream then and change the default there? My concern is that we currently ship a blank configuration and rely on defaults and auto-discovery; I wouldn’t want to erode that with all sorts of customizations.</div></div><div dir="auto"><br></div><div dir="auto">Alex</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed 11. Mar 2020 at 19.19, Otavio Salvador <<a href="mailto:otavio.salvador@ossystems.com.br">otavio.salvador@ossystems.com.br</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Alex,<br>
<br>
On Wed, Mar 11, 2020 at 2:22 PM Alexander Kanavin<br>
<<a href="mailto:alex.kanavin@gmail.com" target="_blank">alex.kanavin@gmail.com</a>> wrote:<br>
> I do not think we should be overriding upstream defaults like this. If your use case is different, you can always provide a custom weston.ini through a bbappend.<br>
<br>
I'd like to argue why, in this case, it makes sense.<br>
<br>
The weston is getting more and more adoption and often we use it on<br>
devices that do not have keyboard and mouse connected. The default<br>
configuration file, on OE-Core, should be adequate for common use<br>
cases as we see on embedded devices and failing to start just because<br>
we lack input devices is far from user-friendly.<br>
<br>
We do have a bbappend our multiple customer layers and as it has<br>
become common we'd like to upstream it as we used quite some time to<br>
understand why it was failing when we first faced it.<br>
<br>
-- <br>
Otavio Salvador O.S. Systems<br>
<a href="http://www.ossystems.com.br" rel="noreferrer" target="_blank">http://www.ossystems.com.br</a> <a href="http://code.ossystems.com.br" rel="noreferrer" target="_blank">http://code.ossystems.com.br</a><br>
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750<br>
</blockquote></div></div>