On Mon, Aug 1, 2016 at 4:14 PM, Simon Fels <morp...@gravedo.de> wrote: > On 01.08.2016 16:06, Bruce Ashfield wrote: >> >> >> On Mon, Aug 1, 2016 at 7:32 AM, Simon Fels <morp...@gravedo.de >> <mailto:morp...@gravedo.de>> wrote: >> >> Hey everyone, >> >> I've worked on a new layer recently which brings snaps to any >> Yocto/OpenEmbedded based system. >> >> If you have never heard about snaps yet you will find most details at >> http://snapcraft.io/ but generally snaps are a new packaging format made >> with security and fast updates in mind and allows applications to be >> packaged once but run everywhere no matter of the distribution used or a >> particular device type. >> >> The layer is currently named meta-snappy and is available at >> https://github.com/morphis/meta-snappy >> >> >> I had a quick browse this morning, and one question that jumped to mind was >> if the oe-meta-go layer was causing problems for go/go-cross support ? I was >> carrying some go/go-inc changes in meta-virtualization as well, but recent >> reports >> are that oe-meta-go should work for everything now. >> >> I'm just asking, since it doesn't make sense for meta-virt or other layers to >> continue to carry go build infrastructure when it could be unified. > When I started to put meta-snappy together I ran into different problems > with oe-meta-go and then reused what you put into meta-virt. I have the > point on my TODO list to check if we can just switch to oe-meta-go > rather than shipping go-cross on our own.
The meta-golang seems to be the most up to date one. Likely the best one to try to converge as a single place for go-cross provider. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
