Opened 4 years ago

Last modified 5 weeks ago

#61192 new defect

Lots of golang ports are downloading dependencies at build time — at Initial Version

Reported by: amake (Aaron Madlon-Kay) Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: annie aws-vault certigo chezmoi cloudmonkey copilot croc elvish evans fzf gitqlite glow go-migrate golangci-lint gore gotop grpcurl hugo ipfs istioctl jenkins-cli k9s krew kubergrunt kustomize micro mole newreleases pulumi rclone scw staticcheck syncthing tektoncd-cli terragrunt trivy uni up webify wtfutil yq nebula qri

Description

With the introduction of the Go modules system, it's very easy to accidentally make a port that downloads dependencies at build time.

I want to add GOPROXY=off GO111MODULE=off to build.env to prevent this, but there are many ports that currently fail in my testing.

Discover ports using the golang-1.0 portgroup (currently 85): 

find . -name Portfile | xargs grep -l -E 'PortGroup +golang' | xargs -n 1 dirname | xargs -n 1 basename

Of those, ports that failed to build with GOPROXY=off GO111MODULE=off appended to build.env:

  • glow
  • uni
  • yq
  • krew
  • fzf
  • chezmoi
  • gotop
  • pulumi
  • k9s
  • up
  • istioctl (due to #61184)
  • certigo
  • wtfutil
  • cloudmonkey
  • kubergrunt (already reported in #61185)
  • terragrunt
  • hugo
  • micro
  • elvish
  • trivy
  • aws-vault
  • annie
  • mole
  • scw
  • croc
  • ipfs
  • rclone
  • syncthing
  • evans
  • gitqlite
  • kustomize
  • webify
  • newreleases
  • go-migrate
  • golangci-lint
  • tektoncd-cli
  • gore
  • copilot
  • jenkins-cli
  • staticcheck
  • grpcurl

I have not yet checked that each of these failures is from being unable to download dependencies, as opposed to e.g. something more esoteric about GO111MODULE.

Change History (0)

Note: See TracTickets for help on using tickets.