From: James Hilliard <james.hilliard1@gmail.com>
To: buildroot@buildroot.org
Cc: Christian Stewart <christian@aperture.us>,
James Hilliard <james.hilliard1@gmail.com>
Subject: [Buildroot] [PATCH v7 1/3] package/pkg-golang.mk: use golang toolchain default GOPROXY
Date: Fri, 2 Oct 2026 13:26:46 -0600 [thread overview]
Message-ID: <20261002192648.3757582-1-james.hilliard1@gmail.com> (raw)
This change sets the default GOPROXY value to match Go's built-in
default of "https://proxy.golang.org,direct" which provides several
benefits:
- Avoid package breakages due to missing module sources
- Better alignment with upstream Go toolchain defaults
- Faster downloads via the proxy compared to direct Git clones
- Maintains reproducible builds through Go's module checksum validation
The default value from the toolchain can be read with "go env GOPROXY"
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
package/pkg-golang.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/pkg-golang.mk b/package/pkg-golang.mk
index ffd50adecc..26da7be71b 100644
--- a/package/pkg-golang.mk
+++ b/package/pkg-golang.mk
@@ -101,7 +101,7 @@ $(2)_POST_PATCH_HOOKS += $(2)_GEN_GOMOD
$(2)_DOWNLOAD_POST_PROCESS = go
$(2)_DL_ENV += \
$$(HOST_GO_COMMON_ENV) \
- GOPROXY=direct \
+ GOPROXY="https://proxy.golang.org,direct" \
$$($(2)_GO_ENV)
# If building in a sub directory, do the vendoring in there
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-10-02 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 19:26 James Hilliard [this message]
2026-10-02 19:26 ` [Buildroot] [PATCH v7 2/3] package/pkg-golang.mk: make GOPROXY configurable James Hilliard
2026-10-02 19:26 ` [Buildroot] [PATCH v7 3/3] package/tailscale: bump to version 1.102.5 James Hilliard
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=20261002192648.3757582-1-james.hilliard1@gmail.com \
--to=james.hilliard1@gmail.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox