3 ms·

So you’re saying that even if your app compiles to a single binary, that’s a requirement? I understand why, but it’s indeed quite a pain.

• francislavoie 7y ago
  Yup. It's a bummer. https://go-team.pages.debian.net/packaging.html https://go-team.pages.debian.net/packaging.html
  • thayne 7y ago
    Unless I'm missing something, that only says you need to package all dependencies if it is a library. Which means you could make a binary-only statically compiled package without adding a bunch of dependencies right? Of course, that isn't helpful if you need to compile with extra plugins, but in that case you are probably using standard go tools and not apt packages anyway.
    • francislavoie 7y ago
      See https://github.com/Debian/dh-make-golang/issues/131 https://github.com/Debian/dh-make-golang/issues/131 We were specifically told that we would need to have all our dependencies packaged. Debian needs to be able to validate that it was built entirely from source code from library packages, not from a binary built externally.