<html><head></head><body><div>On Tue, 2017-02-07 at 17:35 +0000, Burton, Ross wrote:</div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 7 February 2017 at 04:24, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote type="cite"><div id=":3zt" class="a3s aXjCH m15a16d210a62cc87">This is converging the recipes for go from<br>
meta-virtualization and oe-meta-go<br></div><br></blockquote></div><br>I'm still of the opinion that this should be in meta-go, not oe-core...</div></div>
</blockquote><div><br></div><div>FWIW I disagree. Go is a popular systems language and we're increasingly supporting a wide-array of systems with OE (from iot to ivi and beyond). </div><div><br></div><div>Go is already in wide enough use and duplicated in enough layers that we would be doing folks a favour by including it in OE-Core and our build/test cycle.</div><div><br></div><div>Joshua</div></body></html>