<p><br>
On Jul 7, 2012 7:14 PM, "Robert P. J. Day" <<a href="mailto:rpjday@crashcourse.ca">rpjday@crashcourse.ca</a>> wrote:<br>
><br>
> On Sat, 7 Jul 2012, Saul Wold wrote:<br>
><br>
> > On 07/07/2012 08:43 AM, Robert P. J. Day wrote:<br>
> > ><br>
> > > i recall that there's a current request to be able to list the<br>
> > > packages and versions that relate *just* to the current target and<br>
> > > machine, so i'm looking for any other way to do this so students can<br>
> > > see the difference for themselves.<br>
> > ><br>
> > > for example, i'm starting with a configuration of "qemuarm", and i<br>
> > > can do a fetchall:<br>
> > ><br>
> > > $ bitbake -c fetchall core-image-minimal<br>
> > ><br>
> > > and let that run. so far, so good -- i've now fetched everything<br>
> > > required for this target. if i repeat that command, obviously,<br>
> > > nothing should change, and it doesn't. (i don't even have to build<br>
> > > the target, i'm just doing fetching for now.)<br>
> > ><br>
> > > now let's say i add to my local.conf:<br>
> > ><br>
> > > IMAGE_INSTALL_append = " strace"<br>
> > ><br>
> > > i suspect there's an easier way to see this, but if i want to *prove*<br>
> > > that the strace recipe would be part of the build, i can do:<br>
> > ><br>
> > > $ bitbake -c fetchall -n core-image-minimal [dry run]<br>
> > ><br>
> > Have you tried bitbake -e which prints out all the variables and python<br>
> > functions, you can then grep for ^IMAGE_INSTALL or what ever you expect to<br>
> > affect by your change<br>
> ><br>
> > Sau!<br>
><br>
> oh, that's already on my list, i was just trying to dig up<br>
> clever(?) ways to show *only* what would change.</p>
<p>If you don't know what would change just save bitbake -e before and after changes and meld / diff.</p>
<p>@g<br>
</p>