[meta-virtualization] Fwd: oe-meta-go provider
Bruce Ashfield
bruce.ashfield at gmail.com
Mon Apr 24 05:29:02 PDT 2017
On Mon, Apr 24, 2017 at 6:36 AM, Theodor Gherzan <theodor at resin.io> wrote:
> The oe-meta-go provider that this layer suggest (
> https://github.com/errordeveloper/oe-meta-go) seems to no longer be
> maintained. Is it safe to use a new version of it (
> https://github.com/mem/oe-meta-go)? This was forked from the one your
> layer suggest but is actually maintained.
>
Depends on the branch you are using of meta-virt.
If it is anything but master, I haven't been testing it with anything but
the go support we have in meta-virt.
If it is master, only oe-core is needed (and all that I've been testing).
Bruce
>
> Best regards,
> Theodor Gherzan
>
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-virtualization/attachments/20170424/ae264877/attachment.html>
More information about the meta-virtualization
mailing list