On 17/03/2011 14:43, Esben Haabendal wrote: > On Thu, 2011-03-17 at 11:18 +0000, Phil Blundell wrote: >>> 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. >> The benefits of solving the problem are clearly very great, but I >> don't think OE itself is really in a position to embrace a "big bang" >> kind of change which would require redefining all the build >> dependencies. I think we need to find a technological solution which >> will work with our current DEPENDS scheme. > I know that this seems to be the general consensus in OE, but I do not > agree with it. Sometimes architectural work requires working out the > details on a branch, and then when it is mostly done, do the "big bang" > which will then not really be that "big" anymore, as most of the issues > have been resolved. > > Is OE really in a position to permantly settle for something suboptimal > in such a central area? > I would suggest a branch of oe-core is the ideal place to do this work. It can be proved on oe-core then rolled out to meta-oe at a later date.
Graeme _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
