On Fri, 2011-03-11 at 12:04 +0100, Steffen Sledz wrote: > which occurred sometimes depending on build order (not in clean > package only builds).
I would like to raise awareness of the underlying problem here. The current dependency/staging model of OE basically has this feature that a build can be influenced not only by it's own dependencies, but also what has been build before it (or not). I strongly believe that this has to be fixed on the architectural level, and not just on a case-by-case level as is currently needed. I haven't received much feedback on the preivous posting about the per-recipe staging principle implemented in OE-lite, but I decided to take this opportunity to re-iterate the fact that the OE-lite implementation of staging and build dependencies eliminates this problem. I am still very much interested in discussing how to move this technology from OE-lite to OE, but as it impacts all recipe metadata (build dependencies has to be redefined), OE community at a large really needs to value the benefits of solving this problem. Best regards, Esben _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
