<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Aug 17, 2014 at 10:55 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Sun, 2014-08-17 at 10:33 +0200, Jacob Kroon wrote:<br>
> On Sat, Aug 2, 2014 at 10:54 AM, Richard Purdie<br>
> <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br>
> [This is an RFC which depends on a patch to bitbake to<br>
> operate]<br>
><br>
> Currently, we have a mess of dependencies for pixbufcache and<br>
> even then<br>
> it breaks since they might be controlled by PACKAGECONFIG.<br>
><br>
> Instead, this patch proposes an alternative approach where we<br>
> allow<br>
> "fixups" from a sceneQueueComplete() event at the end of the<br>
> setscene<br>
> process. We signal the need for these using simply stamp<br>
> files.<br>
><br>
> The one downside is that the processing code needs to be in a<br>
> global<br>
> event handler like base.bbclass rather than<br>
> pixbufcache.bbclass but this<br>
> is probably a price worth paying to avoid the dependency mess?<br>
><br>
> Signed-off-by: Richard Purdie<br>
> <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>><br>
><br>
><br>
><br>
> Instead of having the sstate_postinst() touch "needpixbuf", could we<br>
> make it write out the actual script that needs to be executed ?<br>
><br>
> Then base.bbclass could iterate over any scripts installed by any<br>
> sstate_postinst() and execute them. At least this would better isolate<br>
> the pixbuf-code to pixbufcache.bbclass, and make the snippet in<br>
> base.bbclass more generic.<br>
<br>
</div></div>It does become trickier to avoid races when writing out that script.<br>
Touching the file is rather easy from a lock perspective :)<br>
<br></blockquote><br></div>Ah.. right, I didn't think of that. Is there no framework already in place in bitbake/OE/Python that we could use for doing atomic write-out-file-if-it-doesn't-exist-yet ?<br></div></div>