Re: [PATCH 1/3] go: Add recipes for golang compilers and tools

[Mark Asselstine <mark.asselstine@windriver.com>]

On Wednesday, February 8, 2017 9:17:48 AM EST Paul Eggleton wrote:
> On Tuesday, 7 February 2017 9:44:46 AM NZDT Khem Raj wrote:
> > On Tue, Feb 7, 2017 at 9:35 AM, Burton, Ross <ross.burton@intel.com> 
wrote:
> > > On 7 February 2017 at 04:24, Khem Raj <raj.khem@gmail.com> wrote:
> > >> This is converging the recipes for go from
> > >> meta-virtualization and oe-meta-go
> > > 
> > > I'm still of the opinion that this should be in meta-go, not oe-core...
> > 
> > I think we have to make multiple layers agree on using one layer
> > I find atleast 3 which carry go recipes along with, if its in OE-Core
> > either these layers become redundant or layers which are housing go
> > recipes for
> > different purpose like meta-virtualization can then drop the compiler
> > recipes it will be easier from consolidation point of view.
> > 
> > if we dont want to take it into OE-Core, we should create a new layer
> > meta-golang on yp git and then help request community to converge to
> > it, it still can be ignored by layers.
> 
> Have we tried asking all of the various people involved if they'd mind
> working together? If not, I have my doubts as to whether putting it in
> OE-Core is going to entirely resolve the situation.

I have done a bunch of the work for go support in meta-virtualization. I am 
currently doing some updates around issues which per recipe sysroots 
uncovered. I think we would be fine moving our support out of meta-virt if 
support was somewhere where our changes would be taken/considered and merges 
would be done in a timely manner, something that hasn't always been the case 
with the previous attempts to centralize go.

Feel free to ping me on this, I will try to find time to try it out and will 
work to get it to the point where we can consider removing parts/all from 
meta-virt.

MarkA 

> 
> Cheers,
> Paul