Hello Alex, On Wed, Mar 11, 2020 at 2:22 PM Alexander Kanavin <[email protected]> wrote: > 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.
I'd like to argue why, in this case, it makes sense. The weston is getting more and more adoption and often we use it on devices that do not have keyboard and mouse connected. The default configuration file, on OE-Core, should be adequate for common use cases as we see on embedded devices and failing to start just because we lack input devices is far from user-friendly. We do have a bbappend our multiple customer layers and as it has become common we'd like to upstream it as we used quite some time to understand why it was failing when we first faced it. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
