[oe] [OE-core] Buildhistory, was Re: do rootfs does not create log files

[Richard Purdie]

On Mon, 2012-02-06 at 10:04 +0100, Andreas Müller wrote:
> On Mon, Feb 6, 2012 at 8:46 AM, Koen Kooi <koen at dominion.thruhere.net> wrote:
> >
> > Op 5 feb. 2012, om 23:16 heeft Andreas Müller het volgende geschreven:
> >
> >> Hi,
> >>
> >> is it a bug or a feature that do_rootfs does not create the package
> >> information (packed_files / packages ..) in a deploy sub-folder did I
> >> miss a switch for this?
> >
> > It's this one: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-angstrom/commit/?id=370a884b2372b7ddd5f0876119b5f28a2b20074f
> >
> > The matching commit it missing, but you can add something like this to your local.conf:
> >
> > INHERIT += "buildhistory"
> > BUILDHISTORY_COMMIT = "1"
> > BUILDHISTORY_DIR = "/data/ssd/OE/buildhistory/"
> >
> > That will create a tree that looks like https://github.com/Angstrom-distribution/buildhistory/. It it's missing a feature that you were using in testlab, let us know and Paul or I will try to add it to buildhistory.
> >
> > regards,
> >
> > Koen
> Thanks for the info - will give buildhistory a test.
> 
> Without having experience on buildhistory I have a question: As you
> might know there was a discussion about the order of packages in
> bitbake.conf [1]. I have no idea of the workflow for this issue:
> 
> 1. Enable buildhistory as said above
> 2. Build from scratch
> 3. change the PACKAGES order in bitbake.conf
> 4. ??
> 
> If I just rebuild without any PR-bumps I assume buildhistory can do
> nothing for me. Correct?

Do two build from scratch, one with the changed PACKAGES and one
without. Keep the same build history data in both builds. You'll then
see the differences between them recorded.

(Or diff the buildhistory from the two builds).

Cheers,

Richard