4 ms·
Do you happen to know _why_ Debian decided to require that for Go projects? It's so absurdly complicated. I've been looking into .deb packaging for Caddy but i
by francislavoie 7y ago
Do you happen to know _why_ Debian decided to require that for Go projects? It's so absurdly complicated.
I've been looking into .deb packaging for Caddy but it really feels like they require us to jump through too many hoops to make it happen. I'd much rather just ship a prebuilt binary.
- tribaal 7y agoI would love a deb-packaged Caddy as well :(
- francislavoie 7y agoYou'll be happy to know Caddy will have a deb package in the next release (albeit not part of official debian repos), see https://github.com/caddyserver/caddy/pull/3309 https://github.com/caddyserver/caddy/pull/3309
- Foxboron 7y ago>It's so absurdly complicated. Security. Dynamically linking stuff is always going to be better than statically linking. Do you trust upstream to keep track of security issues and rebuild in the absurd dependency tree that is Golang software? Or the multi-year old effort which is the current Debian security team? The reason why it's absurdly complicated is solely on the Golang team, not Debian.