[MacPorts] #61192: Lots of golang ports are downloading dependencies at build time
MacPorts
noreply at macports.org
Wed Sep 23 00:20:44 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):
Replying to [comment:29 herbygillot]:
> Seeing another issue where things fail when `go.vendors` contains:
> - two modules of the same name even though they live in different repos
> - or two or more versions of the exact same module (main project may
require vX, but a dependency uses vY)
I fixed one limitation relating to this recently in
https://github.com/macports/macports-
ports/commit/3ad6f3ce0a0c011466bbd3e076295879f1148975, but there are still
limitations relating to how GitHub names tarballs: tarballs fetched from a
tag ref have the tag's hash in the name, so to identify the extracted
directory you must either
- Specify the hash in addition to the tag (cumbersome), or
- Only use the hash and never a tag (also cumbersome, harder to
understand)
The workaround currently used by both golang-1.0 and github-1.0 portgroups
is to use globs (`${author}-${project}-*`). This works for 99% of cases
but obviously fails in the case of multiple tarballs from the same repo.
--
Ticket URL: <https://trac.macports.org/ticket/61192#comment:31>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list