On 2025/10/21 14:03, Marco van Hulten wrote:
> On Fri, 17 Oct 2025 10:48:23 +0100 Stuart Henderson wrote:
> > On 2025/10/17 10:45, Stuart Henderson wrote:
> > > not a very satisfying diff, but try this  
> > 
> > oh, scratch that, it was actually recursing rather than just taking a
> > long time to build...
> 
> I'm not sure if I understand.
> 
> Should the additional DISTFILES.v provide all the things that it
> otherwise tries to get from github.com and golang.org during 'make
> build'?

one way or another, everything needed during build must be fetched via
DISTFILES variable/s, either directly or via what go.port.mk provides.

the tricky bits are finding the right place for the various files (the
originals and the extra ones), and then finding a way to get make to
do that without go.port.mk scrambling your brain.

> What is still failing?

it was looping due to the symlink.

> I wanted to run 'make pre-build' separately, but then PORTS_PRIVSEP
> does not do what I expect:

you can't use pre/post/do-xxx targets separately like that, only as part
of "make patch", "make", "make fake", etc. it's simply not supported.