On Sat, Sep 4, 2021 at 09:54 AM, Richard Purdie wrote:<br />
<blockquote>Adding a single keyword every six months to show the layer is active and meant<br />to work with a new release is not in my view a huge maintenance burden compared<br />to showing that the layer is actively maintained and clearly showing which<br />combinations are meant to work.</blockquote>
It's not feasible because if the layer required some extra bbclasses cherry-picked to be support it in the older yocto,<br />then no one can simply add this keyword to mark it's supported with older yocto. This in practise means that despite<br />the layer itself didn't require any changes to be supported in older yocto it will be unconditionally rejected by bitbake.<br /><br />So, in reality it mean that such a layer has to be forked and modified to be accepted by bitbake.<br /><br />I hope this clearly shows why this kind of checking in bitbake is inappropriate.<br /><br />--<br />Regards,<br />Damian