News for hackers. Stuff that matters.
Re:Show HN: Caddy 2 by francislavoie on Monday May 04, 2020 @03:39PM (#23072385)
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 which provides us with free APT repo hosting for open source projects.

Re:Show HN: Caddy 2 by jbverschoor on Monday May 04, 2020 @04:22PM (#23072809)
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.

Re:Show HN: Caddy 2 by francislavoie on Monday May 04, 2020 @04:27PM (#23072864)
Re:Show HN: Caddy 2 by thayne on Tuesday May 05, 2020 @02:26AM (#23077107)
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.

Re:Show HN: Caddy 2 by francislavoie on Tuesday May 05, 2020 @07:18AM (#23078763)
See 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.