some of these symlink commands come from the modules2tuple port used to determine the dependencies from the last go build command. However I found that it does not handle the /Vn version specific items where V0, V1 and V2 were all referenced, these add added by trial and error un til the port built successfully and would run correctly for my testing.

@dmgk You're into Go stuff, can you take a look, please? ^

I'd suggest dropping GH_TUPLE and switching to GO_MODULE instead, something like https://gist.github.com/dmgk/3cd7a4f1c8ef45a7e1cd9f57cf4a466c
Also the "go" directive in go.mod needs to be bumped to at least 1.17 (or golang.org/x/sys downgraded to the version that still supports go1.16), otherwise I'm getting build errors:

# golang.org/x/sys/unix
vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)

switch to go module and amend dependent bitmark-* ports

Harbormaster completed remote builds in B48904: Diff 114623.Dec 29 2022, 8:58 AM

@dmgk thanks for the GO_MODULE suggestion, I had problems with dependent bitmark-* ports.
The only way I found for the present was to override the distinfo in each of their Makefiles.

Is there a better way perhaps?

Uses/go.mk doesn't allow overriding DIST_SUBDIR. Maybe it should, @dmgk ?

In D37877#861036, @arrowd wrote:

Uses/go.mk doesn't allow overriding DIST_SUBDIR. Maybe it should, @dmgk ?

What problem would it solve? In GO_MODULE mode, DIST_SUBDIR serves as a local GOPATH for each port, with nested GOMODCACHE. What would be the reason to move it elsewhere?

In D37877#861035, @hsw_bitmark.com wrote:

@dmgk thanks for the GO_MODULE suggestion, I had problems with dependent bitmark-* ports.
The only way I found for the present was to override the distinfo in each of their Makefiles.

Is there a better way perhaps?

AFAIK, overriding DISTINFO_FILE in slave ports is how it's usually done.

@dmgk So, this is fine to get in?

Looks good to me.

This revision is now accepted and ready to land.Jan 3 2023, 2:46 PM

Closed by commit R11:e2732b2416ec: net-p2p/bitmark: update to 0.15.0 (authored by hsw_bitmark.com, committed by arrowd). · Explain WhyJan 3 2023, 7:38 PM

This revision was automatically updated to reflect the committed changes.

arrowd added a commit: R11:e2732b2416ec: net-p2p/bitmark: update to 0.15.0.