From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Openembedded-core@lists.openembedded.org
Cc: Vyacheslav Yurkov <uvv.mail@gmail.com>
Subject: [langdale][kirkstone][PATCH] go-mod.bbclass: Allow network in do_compile
Date: Thu, 22 Dec 2022 16:02:46 +0100 [thread overview]
Message-ID: <20221222150246.91423-1-uvv.mail@gmail.com> (raw)
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.mail@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!"
+}
--
2.35.1
next reply other threads:[~2022-12-22 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 15:02 Vyacheslav Yurkov [this message]
2022-12-22 16:20 ` [OE-core] [langdale][kirkstone][PATCH] go-mod.bbclass: Allow network in do_compile Richard Purdie
2022-12-22 16:48 ` Bruce Ashfield
2022-12-22 18:39 ` Vyacheslav Yurkov
2022-12-22 19:08 ` Martin Jansa
2022-12-26 9:38 ` Vyacheslav Yurkov
2022-12-26 9:59 ` Martin Jansa
2022-12-29 16:42 ` Vyacheslav Yurkov
2023-01-02 15:40 ` Stefan Herbrechtsmeier
2023-01-03 16:03 ` Lukas Funke
2023-03-12 9:15 ` Martin Jansa
[not found] ` <174BA13431CDE838.27660@lists.openembedded.org>
2023-09-10 21:26 ` Martin Jansa
2023-09-27 13:34 ` Lukas Funke
2023-09-27 14:40 ` Bruce Ashfield
2023-01-12 5:01 ` wonsang.ryu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221222150246.91423-1-uvv.mail@gmail.com \
--to=uvv.mail@gmail.com \
--cc=Openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.