[MacPorts] #61192: Lots of golang ports are downloading dependencies at build time

MacPorts noreply at macports.org
Sat Sep 19 11:47:46 UTC 2020


#61192: Lots of golang ports are downloading dependencies at build time
-------------------------------------------------+-------------------------
  Reporter:  amake                               |      Owner:  (none)
      Type:  defect                              |     Status:  new
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:
Resolution:                                      |   Keywords:
      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                           |
-------------------------------------------------+-------------------------

Comment (by amake):

 Some background:

 I made `go2port` before the modern go module system existed, when there
 were several competing dependency managers (glide, gopkg, glock); it's
 modeled after other portfile generators like `pypi2port` and `cpan2port`.
 I made the golang-1.0 portgroup largely based on other portgroup idioms
 and the peco portfile.

 I am not a golang guy. I just wanted to make and maintain ports for tools
 that happened to be in golang. `go2port` was my first (and last, so far)
 golang project. So it sounds like you have a much better understanding of
 the ecosystem than I do.

 There is no mandate to use either `go2port` or the golang-1.0 portgroup.
 If you have better ideas that better meet MacPorts requirements then by
 all means we should move on.

 The `go mod download -json` output sounds very useful, but I'm not seeing
 a way to use that *within* a portfile that lets MacPorts manage the
 fetching (which is what we're really concerned with here). The best I can
 imagine is using it to generate the distfiles and checksums sections, but
 that's basically what `go2port` already does.

-- 
Ticket URL: <https://trac.macports.org/ticket/61192#comment:8>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list