From 892544396ae63b025493d4efd9b914f5829bd50b Mon Sep 17 00:00:00 2001
From: Phil Pennock <phil@pennock-tech.com>
Date: Tue, 14 Aug 2018 12:55:28 -0400
Subject: [PATCH] Unset GO111MODULE within Gimme itself

Presumably when `GO111MODULE` is set in environ when calling `gimme`,
it's part of generic setup to be used by the Go toolchain when building
the code being CI tested and the intent is not to try to tell Go, when
building from source, that it should be requiring the new Go 1.11 module
semantics.

Forcibly unset `GO111MODULE` in Gimme itself, but do not do anything to
add this to the emitted environment variables.

Without this, `gimme master` currently fails; with this change, it
succeeds.
---
 gimme | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gimme b/gimme
index 03569c2..cac0122 100755
--- a/gimme
+++ b/gimme
@@ -890,6 +890,8 @@ unset GOPATH
 unset GOROOT
 unset CGO_ENABLED
 unset CC_FOR_TARGET
+# GO111MODULE breaks build of Go itself
+unset GO111MODULE
 
 mkdir -p "${GIMME_VERSION_PREFIX}" "${GIMME_ENV_PREFIX}"
 # The envs dir stays small and provides a record of what had been installed