On 8 January 2014 18:44, Philip Balister <phi...@balister.org> wrote: > On 01/08/2014 12:01 PM, Richard Purdie wrote: >> On Wed, 2014-01-08 at 16:09 +0000, Burton, Ross wrote: >>> Hi, >>> >>> Despite a good start this thread got rapidly hijacked, so let's try again! >>> >>> On 24 December 2013 01:09, Philip Balister <phi...@balister.org> wrote: >>>>> 1) Move piglit and deps to oe-core. Piglit is for QA purposes only >>>>> and pushes the boundaries of "core platform". In a sense this is a >>>>> repeat of the discussion we had with Midori... does oe-core contain >>>>> everything needed to sufficiently exercise the core components it >>>>> ships or not? >>>> >>>> I expect Richard will push back on this, and I would support him here. >>> >>> Probably best to let Richard speak for himself here. :) >> >> :) >> >> I have to admit I'm leaning towards pulling in the 4 recipes we need >> since the win is we get to test the GL stacks. >> >> We do support graphics in the core, we also do particularly badly at >> testing it. That is something I think we need to change. piglit lets us >> do that and its not like it has a significant number of dependencies. >> Having a couple more python modules to test the python stack probably >> isn't a bad idea ether. We pruned quite a number of recipes out, this is >> a case where we can add a small number for a significant win. > > Does this mean you will fix the host contamination that occurs when > machines have atals and/or blas devel packages installed :) > > We should probably look carefully at the numpy recipe if we go this route,
I've looked at it enough to know I don't want to look at it anymore. ;) Ross _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core