<div dir="ltr"><div class="gmail_extra">On Thu, Nov 28, 2013 at 3:17 AM, Paul Eggleton <span dir="ltr"><<a href="mailto:paul.eggleton@linux.intel.com" target="_blank">paul.eggleton@linux.intel.com</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wednesday 27 November 2013 11:42:06 Chris Larson wrote:<br>
> On Wed, Nov 27, 2013 at 10:08 AM, Stefan Stanacar <<br>
> <a href="mailto:stefanx.stanacar@intel.com">stefanx.stanacar@intel.com</a>> wrote:<br>
> > This series adds an oe-selftest script, some modules and a new layer<br>
> > meta-selftest.<br>
> > which are meant to help in writing tests (using python unittest) for<br>
> > various<br>
> > <span class="il">bitbake</span> tools/scripts as well as simple output checks or do<br>
> > complete builds with different options (with the emphasis that everything<br>
> > checked<br>
> > is done outside of <span class="il">bitbake</span> context, just like a human would do.) For more<br>
> > details,<br>
> > please see YOCTO #4740.<br>
><br>
> Will this have its own repository like all the other poky integrated<br>
> layers? It really should, in my opinion.<br>
<br>
</div>It really needs to stay in the same place as the tests that rely on it; they<br>
can't work without it. It might be suggested that the tests should go<br>
elsewhere with them; but I don't think that would make sense - we want people<br>
to be able to run these tests easily if they make changes to OE-Core to check<br>
if they have caused any regressions.<br>
<br>
If you have a look at the layer, there's not a lot in it, and I wouldn't<br>
expect a lot to be added in future. One possible change would be to just have<br>
the layer created on the fly in some temporary directory by the tests<br>
themselves, rather than having it in the repository; on the other hand it does<br>
make it a <span class="il">bit</span> more difficult to look into outside of the test environment.</blockquote></div><br>I understand what you’re saying, but if this script is supposed to be generally useful for OE/Yocto, not just Poky, then the poky repository shouldn’t be its definitive location. Further, patches against oe-core should be submitted against the oe-core repository, not the poky repository, and anything poky specific should go to the poky list.<br>
-- <br>Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>