Thanks for the response, Richard.
On 25 May 2016 at 10:25, Richard Purdie <[email protected]>
wrote:
> ...
>
> I have wondered if we should make images behave a bit more like sstate,
> in that they could write to an intermediate directory which is then
> moved into position.
>
> That way, toaster could know that a set of files come from a given task
> for sure.
>
> Its obviously a pretty invasive change in behaviour but also partly in
> keeping with the rework of the image generation we've been pursusing.
>
> Is it just the do_image_* output we have the issue with?
>
We need to know about all of the files in tmp/deploy/images/${MACHINE},
both the images and any other files which are produced.
We also need to know about SDK artifacts (I can't recall if they end up
there or somewhere else).
I have had a quick look at buildhistory.bbclass, and could use that to
write some useful stuff out to a file in the buildhistory directory, such
as the image name and image fstypes. I could then figure out from that
which image files were produced by the build, which I think would be an
improvement over what we have.
However, we still have the issue of associated artifact files and how we
get those. In particular, we need to be able to tell when a file would have
been produced if it wasn't already there. Could we use sstate for that?
Cheers,
Elliot
>
> Cheers,
>
> Richard
>
>
>
--
Elliot Smith
Software Engineer
Intel Open Source Technology Centre
--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster
