Need help with lazy module loading & gvisor

[John Goerzen <jgoerzen@complete.org>]

Hi folks,

At least two Debian packages use https://github.com/inetaf/netstack,
which was a popular pure-Go TCP/IP networking stack.  It was a fork of
gvisor, pulling out the networking stack from what was a more ambituous
pure Go operating system project.

At that URL, upstream says "This repo is no longer maintained. As of Go
1.17 and its lazy module loading we no longer need it, so we now just
use upstream gVisor directly."

gVisor is indeed /huge/.  Before one of the upstreams had switched to
netstack, I had attempted to package gVisor and gave up.  The sheer
number of unpackaged dependencies wouldn't have been suitable for me,
and as I recall there were build system pecularities also.  I'm a guy
that doesn't know Go but has packaged up some Go software and that was
too much in the weeds.

Now upstreams are switching back to gVisor so this need is becoming more
pressing, particularly since netstack and go 1.19 have (declared, at
least) incompatibility.

Would somebody be able to help with this situation?  Is there a way we
can get just the needed bits of gVisor packaged?  Any other ideas here?

Thanks,

John