[OE-core] [PATCH 1/3] go: Add recipes for golang compilers and tools

Matt Madison matt at madison.systems
Wed Feb 8 12:46:49 UTC 2017


On Tue, Feb 7, 2017 at 12:17 PM, Paul Eggleton
<paul.eggleton at linux.intel.com> 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 at intel.com> wrote:
>> > On 7 February 2017 at 04:24, Khem Raj <raj.khem at 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.

As the meta-golang maintainer, I'd be happy to help with converging, whether
it's a separate layer or pulled into OE-Core.

-Matt

>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



More information about the Openembedded-core mailing list