4 ms·
You may already know this, but it's very tricky to package Golang projects in official debian repos because they require that every dependency be a separate pac
by francislavoie 6y ago
You may already know this, but it's very tricky to package Golang projects in official debian repos because they require that every dependency be a separate package. This is a ton work both upfront and to maintain in the long-term, so we haven't made much progress on that front.
We'd love to get some help from people who are more comfortable with the debian ecosystem though! It's definitely something we want to achieve, but for the short term we had to make the decision to simply release the .deb via https://gemfury.com https://gemfury.com which provides us with free APT repo hosting for open source projects.
- jbverschoor 6y agoSo 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 6y agoYup. It's a bummer. https://go-team.pages.debian.net/packaging.html https://go-team.pages.debian.net/packaging.html
- thayne 6y agoUnless 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 6y agoSee 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.