Date: Fri, 05 Dec 2025 12:27:29 +0000 From: bugzilla-noreply@freebsd.org To: go@FreeBSD.org Subject: [Bug 291375] Mk/Uses/go.mk: how not to use a GOPROXY? (GOPROXY=direct) Message-ID: <bug-291375-42334-n5zC5sX5LP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-291375-42334@https.bugs.freebsd.org/bugzilla/> References: <bug-291375-42334@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291375 --- Comment #5 from Benjamin Takacs <nimaje+fbz@bureaucracy.de> --- Created attachment 265878 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=265878&action=edit special case GO_GOPROXY = direct (In reply to Adam Weinberger from comment #4) As already written in comment #3 it works just fine (yes in poudriere) as the fetching still happens in the fetch phase. Go just uses git to do the fetching, so we need to add that to FETCH_DEPENDS. Of the ports I personally build only security/snowflake-tor failed and that was because some dependency of it vanished and GOPROXY was hidding that, so I consider that an improvement. (The vanished dependency lead me to find out that security/snowflake-tor is outdated and opening bug 291387) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291375-42334-n5zC5sX5LP>