<div dir="ltr"><div class="gmail_extra">On Sun, Aug 9, 2015 at 8:18 PM, Chen Qi <span dir="ltr"><<a href="mailto:Qi.Chen@windriver.com" target="_blank">Qi.Chen@windriver.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":11n" class="a3s" style="overflow:hidden">When publishing SDK, what we want is basically its metadata and sstate<br>
cache objects. We don't want the SDK to be prepared with running <span class="il">bitbake</span><br>
as it takes time which reproduces meaningless output for the published SDK.<br>
<br>
So this patch adds an option to allow for SDK to be extracted without<br>
preparing the build system.<br>
<br>
Signed-off-by: Chen Qi <<a href="mailto:Qi.Chen@windriver.com">Qi.Chen@windriver.com</a>></div></blockquote></div><br>I expect the intent behind the preparation was for it to be a build from 100% sstate, but that’s not actually the case on all systems. If that’s the case, maybe it should be run with locked sigs and ignore failure, to avoid doing a real from-scratch build at install time.<br>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>