Ebuilds using the go-module eclass are different from most other ebuilds, because they have to include every go dependency. With some luck, the project will have a vendor/ directory and no special action will be needed. If it doesn't, in the short-term, the dependencies will have to be packaged manually. But longer term, try to convince upstream to generate a tarball in CI.
Hi, I want to package it for Gentoo Linux, I tried to add compiled Go software - but they do not like it. This is the quote from the Gentoo Wiki: