From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mail.openembedded.org (Postfix) with ESMTP id 2F9FF60602 for ; Wed, 8 Feb 2017 13:53:05 +0000 (UTC) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga101.fm.intel.com with ESMTP; 08 Feb 2017 05:53:06 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,346,1477983600"; d="scan'208,217";a="56562313" Received: from jlock-mobl1.ger.corp.intel.com ([10.252.16.172]) by orsmga004.jf.intel.com with ESMTP; 08 Feb 2017 05:53:04 -0800 Message-ID: <1486561983.3754.4.camel@linux.intel.com> From: Joshua Lock To: "Burton, Ross" , Khem Raj Date: Wed, 08 Feb 2017 13:53:03 +0000 In-Reply-To: References: <20170207042405.22707-1-raj.khem@gmail.com> X-Mailer: Evolution 3.22.4 (3.22.4-2.fc25) Mime-Version: 1.0 Cc: OE-core Subject: Re: [PATCH 1/3] go: Add recipes for golang compilers and tools X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 13:53:06 -0000 Content-Type: multipart/alternative; boundary="=-0PqxhnkPziqMIFKMYQhx" --=-0PqxhnkPziqMIFKMYQhx Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit On Tue, 2017-02-07 at 17:35 +0000, Burton, Ross wrote: > On 7 February 2017 at 04:24, Khem Raj 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... 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).  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. Joshua --=-0PqxhnkPziqMIFKMYQhx Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit
On Tue, 2017-02-07 at 17:35 +0000, Burton, Ross 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...

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). 

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.

Joshua
--=-0PqxhnkPziqMIFKMYQhx--