Hello,<br><br>There will be a how to integrate proprietary binary overlays onto LEBs <span> at the Connect,<br><a href="https://blueprints.launchpad.net/linaro-android/+spec/linaro-platforms-lc4.11-android-acceleration" target="_blank">https://blueprints.launchpad.net/linaro-android/+spec/linaro-platforms-lc4.11-android-acceleration</a><br>



<br>The plan is to have a discussion about the following cases:<br></span><ol><li><span>The blocking factors on including binaries in our android build:<br></span></li><ul><li>Binaries available on a login protected vendor or third party site.</li>



<li>
Binaries provided for download behind a click through form.</li><li>
Binaries available for download freely, but requiring user to accept a click-through license upon install.</li></ul><li>Open discussion on defining a Linaro Android Overlay package format to support overlay files which could support</li>



<ul><li>A license text file alongside.</li><li>Means for User acceptance or acknowledgement of included license text.</li></ul><li>Tools to support installation of these packages by humans and Lava.</li><li>LAVA to support managing LEBs with overlays.</li>


</ol>I would like to invite the android team and members of landing team who are aware of the licensing terms for proprietary binaries, members from validation team to help us come up with a plan on how we can integrate these proprietary components.<br>


<br><br>Thanks,<br>Vishal<br>