On 2017-02-08 14:53, Joshua Lock wrote:
On Tue, 2017-02-07 at 17:35 +0000, Burton, Ross wrote:
On 7 February 2017 at 04:24, Khem Raj <raj.k...@gmail.com
<mailto:raj.k...@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.
I agree - if ruby is OE-core worthy, go most certainly is.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
