Hi,
You'll quickly find out that the upstream Makefile does not handle
anything, it makes a go get call, and go get attempts to download things
directly from the internet. So, it is completely useless in a Fedora
context.
So your real alternative is between using the Fedora automation, or
handcrafting in your spec file all the things needed for building in a
secure and managed environment, that your upstream made no provision
for.
Also, I see your upstream has already converted to go modules. This is
going to be a problem for you because right now Fedora does not handle
go modules (and upstream gave up on making module mode the default in Go
1.13 a couple of weeks ago, because module tooling is missing too many
pieces right now, not just Fedora-side; right now go modules are only
suitable for direct dev builds on non-production workstation
environments).
So, basically, to get anything done this year, you need to forget about
the upstream makefile, and convert the upstream build mode to classical
GOPATH building mode (unless you want to work with us and Go upstream to
finish tooling for Go module mode, which would be awfully nice, but most
people do not want to get involved at this level).
Regards,
--
Nicolas Mailhot
_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx
