Hi Chris / Qi, On Monday 10 August 2015 08:39:01 Christopher Larson wrote: > On Sun, Aug 9, 2015 at 8:18 PM, Chen Qi <qi.c...@windriver.com> wrote: > > When publishing SDK, what we want is basically its metadata and sstate > > cache objects. We don't want the SDK to be prepared with running bitbake > > as it takes time which reproduces meaningless output for the published > > SDK. > > > > So this patch adds an option to allow for SDK to be extracted without > > preparing the build system. > > > > Signed-off-by: Chen Qi <qi.c...@windriver.com> > > 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.
I agree this is definitely a problem. In fact, I'm fairly sure the locked sigs functionality isn't working as it was originally intended to - last I checked it looked like it was warning and then going ahead and running the task; by default it was supposed to just extract the sstate package. I think we'll need to deal with that separately as all this patch does is make the extraction optional (in order to support the publishing script). As an aside it would be nice if we could hide this -n option in the help when not building the extensible SDK, but on the other hand refactoring things so that would be possible would likely be more effort than it's worth. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
