On Thu, Dec 22, 2022 at 11:20 AM Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > > On Thu, 2022-12-22 at 16:02 +0100, Vyacheslav Yurkov wrote: > > This is a workaround to allow using go-mod until a proper solution is in > > place. Possible solutions were discussued ealier this year in these > > threads: > > > > https://lists.openembedded.org/g/openembedded-core/topic/89464905 > > https://lists.openembedded.org/g/openembedded-architecture/topic/90782883 > > > > Signed-off-by: Vyacheslav Yurkov <uvv.m...@gmail.com> > > --- > > meta/classes-recipe/go-mod.bbclass | 5 +++++ > > 1 file changed, 5 insertions(+) > > > > diff --git a/meta/classes-recipe/go-mod.bbclass > > b/meta/classes-recipe/go-mod.bbclass > > index 61571596bc..da9a583288 100644 > > --- a/meta/classes-recipe/go-mod.bbclass > > +++ b/meta/classes-recipe/go-mod.bbclass > > @@ -24,3 +24,8 @@ inherit go > > > > GO_WORKDIR ?= "${GO_IMPORT}" > > do_compile[dirs] += "${B}/src/${GO_WORKDIR}" > > +do_compile[network] = "1" > > + > > +do_compile:prepend() { > > + bbwarn "Using go-mod enables network during compilation to be able to > > fetch dependencies. This breaks reproducibility of the build!" > > +} > > This patch is not in master and is not a backport therefore not > eligible for kirkstone/langdale. >
'nor should it go to master. If someone wants to allow go to fetch sources during builds, it needs to be done in their own layers. Bruce > Cheers, > > Richard > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#174969): https://lists.openembedded.org/g/openembedded-core/message/174969 Mute This Topic: https://lists.openembedded.org/mt/95827446/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
