<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 11 November 2016 at 16:02, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":mg" class="a3s aXjCH m158543a73aeac59d">Nothing thats enabled in OE-Core depends on go yet, however, thats not<br>
always the reason<br>
for something to be in OE-Core, if you look out, you will see there is<br>
no single layer for golang ( I see atleast 5 )<br>
support, each one of them is done differently, some are better than<br>
others depending upon what you need,<br>
This causes a lot of confusion for users who have golang needs.<br>
golang is a fast growing language being adopted in verticals where OE is used,<br>
This would offer a consolidated place for golang in OE ecosystem.</div></blockquote></div><br>I'm not a massive fan of throwing everything into oe-core, attempting to stop the proliferation of go layers and having everyone agree that a single layer hosted at git.yp or whatever is canonical (even if they decide to copy and paste from it, meta-virtualisation I'm looking at you...) seems more logical.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>