We don't want to just disable the proxy, we want to disable any network
fetches, setting GOPROXY to an invalid url/scheme currently has that effect.
--
Sent from a phone, apologies for poor formatting.
On 16 September 2019 19:55:56 Eric Auge <[email protected]> wrote:
Hello,
I think I saw an update of lang/go to 1.13, which introduce this
modules probing "stuff", read/taken from https://golang.org/doc/go1.13
:
"""
Users who cannot reach the default proxy and checksum database (for
example, due to a firewalled or sandboxed configuration) may disable
their use by setting GOPROXY to "direct",
and/or GOSUMDB to "off". go env -w can be used to set the default
values for these variables independent of platform:
go env -w GOPROXY=direct
go env -w GOSUMDB=off
"""
which seems would default to the commonly known (aka before go modules
and proxy bla) behaviour of the "go get" command,
using the cache first and then trying to resolve dependencies remotely
if a remote path is given and not present in the cache (if i'm not
wrong and if they honor their doc).
May be those variables could be of use? but may be I misunderstood the problem.
HTH,
Rgs,
Eric.
On Fri, Sep 13, 2019 at 10:05 PM Evan Silberman <[email protected]> wrote:
Stuart Henderson <[email protected]> wrote:
> +MAKE_ENV += GOPROXY=invalid://ports.should.not.fetch.at.buildtime/
Got sufficiently curious to check if the URI scheme example:// is
reserved and lo and behold it is. Might as well use it here?
https://tools.ietf.org/html/rfc7595#page-14
Evan Silberman
