From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 26C4F6FFEA for ; Fri, 11 Nov 2016 18:04:39 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id uABI3eih002952; Fri, 11 Nov 2016 18:04:37 GMT Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zUOzYoOnU3Hm; Fri, 11 Nov 2016 18:04:37 +0000 (GMT) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id uABI4Yjp003051 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 11 Nov 2016 18:04:35 GMT Message-ID: <1478887474.23123.233.camel@linuxfoundation.org> From: Richard Purdie To: Alexander Kanavin , openembedded-core@lists.openembedded.org Date: Fri, 11 Nov 2016 18:04:34 +0000 In-Reply-To: References: <20161110003935.1858-1-raj.khem@gmail.com> X-Mailer: Evolution 3.18.5.2-0ubuntu3 Mime-Version: 1.0 Subject: Re: [PATCH 1/2] 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: Fri, 11 Nov 2016 18:04:40 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit On Fri, 2016-11-11 at 15:10 +0200, Alexander Kanavin wrote: > On 11/10/2016 02:39 AM, Khem Raj wrote: > > > > This is converging the recipes for go from > > meta-virtualization and oe-meta-go > Wait a moment, why this should go to oe-core and not to meta-go? IsĀ  > there something in oe-core itself that requires presence of go > compiler? This was something that came up at OEDEM. There are several layers with several attempts at getting this right, most have some issues. Whilst we've been pulling things out of core, we also need to consider things that perhaps should get added. Having this in core would certainly address a number of issues (but is also potentially a maintenance burden). We did agree there that we'd consider this. Obviously input from people not there is welcome though and this does need discussion. I'm leaning moderately in favour of adding it as things stand. Cheers, Richard