David Chisnall

Did you think more about this? Being able to use a separate PGP key pair for the metadata and the blobs would probably be sufficient. That would let you keep...

This turns out to be nontrivial because of the external dependencies that are not on GitHub. FreeBSD ports need to be able to fetch dependencies without using git. For the...

FreeBSD packages must be built by the the FreeBSD package build systems (and must include specific versions of the dependencies - we don't want to find that a rebuild fails...

> Ahh I see - I took a look at other go packages distributed via ports (example) and found they just ship with a pre-compiled binary Not sure why you'd...

Vendoring dependencies is also a bit painful. If you could push a tarball of the versions of the dependencies used to build the releases when you upload the release builds,...

Hi, it looks as if there's been some [work in the generic ports infrastructure to help package go programs](https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/building.html#using-go). I think that will make it (relatively?) easy to handle any...

I have a working package built from the current master as 0.4.p1. I'd prefer to submit it from a release or pre-release tag. Would it be possible to tag the...

For reference, this is the draft port: https://gist.github.com/davidchisnall/d95ec8a2e07ed1f4648a6e937ef11193

I think I just need the release to be tagged. @someone1?

That still shows as a prerelease for me. Is there a release? Once there's one that you're happy with, I can update and submit the port.