I just happen to have two go dependencies using the same link, could only separate by setting different versions to get:
lrwxr-xr-x 1 hsw hsw 50 Nov 1 15:00 go-1.1.7/
lrwxr-xr-x 1 hsw hsw 57 Nov 1 15:00 go-1.1.8/
the tuple that caused this is:
I think migh need to add a the account as part of the link name.
(In reply to Christopher Hall from comment #0)
This is not so much go.mk issue but the issue with how Github packs release tarballs. If json-iterator/go and ugorji/go have the same tag (e.g. v1.1.7), their tarballs will both have go-1.1.7 subdirectory which will then conflict (install sources to the same place) on extract.
The usual workaround in these cases is to replace on of the tags with corresponding commit ID, e.g.
this way json-iterator/go will be extracted to go-1.1.8 and ugorji/go to go-23ab95ef5dc3
modules2tuple probably can be taught to look for these conflicts and do the replacement automatically.
A commit references this bug:
Date: Sat Nov 2 12:35:02 UTC 2019
New revision: 516315
ports-mgmt/modules2tuple: Update to 1.10.0
Approved by: tz (mentor, implicit)
Should be fixed in recent versions of modules2tuple.
Please reopen if this is still an issue.